-
Notifications
You must be signed in to change notification settings - Fork 74
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Change-Id: I847a0022a12a060840f77d171394a21be40ea035
- Loading branch information
1 parent
311f88e
commit 7ab8f90
Showing
1 changed file
with
17 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,17 @@ | ||
This site aims to be a reference repository about 0-day exploits that are | ||
actively used in-the-wild. Since mid-2019, Project Zero has dedicated an effort | ||
specifically to track, analyze, and learn from 0-days that are actively | ||
exploited in-the-wild. Since 2014, Project Zero's mission has been to "make | ||
0-day hard." From that came the goal of our in-the-wild program: "Learn from | ||
0-days exploited in-the-wild in order to make 0-day hard." | ||
|
||
One of the key aspects of our work has been to perform and publish root cause | ||
analyses on each 0-day detected in-the-wild. For the last year, they have been | ||
published on the [Google Project Zero | ||
blog](googleprojectzero.blogspot.com/p/rca.html), but we found that we wanted a | ||
platform that better supports collaboration, history tracking, and updating. So | ||
we've migrated here! | ||
|
||
The goal is for this to be a database of information about exploited 0-days. We | ||
invite pull requests for both new RCAs and updates/edits to existing ones. | ||
Please check out the [Contributing page](contributing.html) for more info. |