知识卡片
未修复漏洞按暴露面处理
已知风险尚无修复时,应判断是否存在受影响代码路径、可利用入口和可行缓解,再安排优先级。更新机器人不能凭空产生补丁,也不能因暂时无版本可升就将风险视为已解决。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
- · 依赖管理实践
原书出处 · 1 处
- · 查看原书依据
fixes have yet to be released. When a new vulnerability is found, there is naturally some amount of time required before the maintainers release a fix to address the vulnerability. Until a fix is found, these vulnerabilities are known as “zero-day vulnerabilities”, because zero days have passed since the fix was published.
参考来源
- 位置:《Effective Machine Learning Teams (David Tan, Ada Leung, David Colls)》第04章《依赖管理实践》(来源项目:a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Effective Machine Learning Teams (David Tan, Ada Leung, David Colls)/_epub-src/OEBPS/ch04.html)
- 结论依据:摘录中关于未修复漏洞按暴露面处理的定义、比较或条件支撑卡片;原书表述不严谨的范围已在覆盖记录逐项限定,不把案例结果外推为普遍结论。
- 原始内容:fixes have yet to be released. When a new vulnerability is found, there is naturally some amount of time required before the maintainers release a fix to address the vulnerability. Until a fix is found, these vulnerabilities are known as “zero-day vulnerabilities”, because zero days have passed since the fix was published.