security-research README

项目的 README,来自 github.com/google/security-research。合并为一个 markdown 文件:README.md。

Security Research

This project hosts security advisories and their accompanying proof-of-concepts related to research conducted at Google which impact non-Google owned code.

We believe that vulnerability disclosure is a two-way street. Vendors, as well as researchers, must act responsibly. This is why Google adheres to a 90-day disclosure deadline. We notify vendors of vulnerabilities immediately, with details shared in public with the defensive community after 90 days, or sooner if the vendor releases a fix.

You can read up on our full policy at: https://www.google.com/about/appsecurity/.

Advisories

The disclosure of vulnerabilities are all in the form of security advisories, which can be browsed in the Security Advisories page.

License & Patents

The advisories and patches posted here are free and open source.

See LICENSE for further details.

Contributing

The easiest way to contribute to our security research projects is to correct the patches when you see mistakes.

Please read up our Contribution policy.

security-research (google/security-research)

正在搜索数据库…

这是什么?这是一个安全公告和概念验证(PoC)漏洞利用代码的合集,涉及 Google 研究人员在非 Google 自有软件中发现的漏洞。
需要安装什么吗,还是只是些文章?只是文章,无需安装:在仓库的 Security Advisories 页面浏览每条公告,公告附带对应的概念验证(PoC)。
这些 PoC 针对的软件是 Google 维护的吗?不是。公告涉及的代码归其他厂商所有,修复由这些厂商完成,Google 则负责发布研究成果和 PoC。
这个内容主要对谁有用?安全研究人员,以及公告中提到的第三方项目的维护者,他们可以借此了解漏洞的成因及修复方式。
Google 为什么要公开其他厂商软件的漏洞利用代码?Google 认为漏洞披露是双向的:厂商必须负责任地处理问题,而细节会在 90 天后公开,以便防御方社区作出响应。
我可以复用 PoC 和补丁吗?可以。这些公告和补丁均以 Apache-2.0 协议免费开源,详见 LICENSE 文件。
我如何帮助改进这个项目?发现补丁有误时予以更正;README 称这是最简单的贡献方式。
作者
google
大小
330 MB
星标
4.7K
更新
提交Nov 18
时长
6年
提交 · 90 天