security-research README

The project's README from github.com/google/security-research. As one markdown file: 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)

Searching Database…

What is this?A collection of security advisories and proof-of-concept exploits for vulnerabilities Google researchers found in software that Google does not own.
Is there anything to install, or is it just write-ups?Just write-ups. Nothing to install: each advisory is browsed on the repo's Security Advisories page and comes with its proof-of-concept.
Does Google maintain the software these PoCs target?No. The advisories cover code owned by other vendors, so the fixes come from those vendors, while Google publishes the research and PoCs.
Who is this mainly useful for?Security researchers, and maintainers of the third-party projects named in the advisories who want to see how a flaw works and how it was fixed.
Why does Google publish exploits for other vendors' software?Google says vulnerability disclosure is a two-way street: vendors must act responsibly, and details go public after 90 days so the defensive community can respond.
Can I reuse the PoCs and patches?Yes. The advisories and patches are free and open source under Apache-2.0, as described in the LICENSE file.
How can I help improve it?Correct the patches when you spot mistakes; the README calls that the easiest way to contribute.
Creator
google
Size
330 MB
Stars
4.7K
Updated
CommitNov 18
Age
6y
Commits · 90 Days