What is Project Zero’s disclosure policy?🔗
When Project Zero finds a new vulnerability, we send a detailed technical description of the issue to the relevant vendor or open source project. This initial vulnerability report includes the following statement:
“This bug is subject to a 90 day disclosure deadline. It will become public after 90 days.”
After 90 days, we will publicly disclose the technical details in our bug tracker.
We plan to move to a 60 day disclosure policy on February 2, 2027.
We plan to move to a 30 day disclosure policy on January 3, 2028.
Within one week, we will publicly share the Project Zero reference number, vendor, product, report date and disclosure deadline on our Reporting Transparency page.
Our policy has a small number of special cases, including in-the-wild exploitation, publication of technical details by a third party and vendor-requested disclosure. The full policy is available here.
The reasoning behind our disclosure policy and Reporting Transparency can be found in our explainer posts.
How does Project Zero publicly disclose a vulnerability?🔗
Our vulnerability discoveries are tracked in the Project Zero issue tracker.
Initially, all of our bug reports are restricted so that only Project Zero team members can see the technical content. When it’s time to disclose, we “derestrict” access to the issue tracker entry for the bug, which means the technical description of the vulnerability will become publicly accessible.
Have there been any cases where an exception to the disclosure deadline policy has been given?🔗
Yes, in 10 out of 2219 cases the disclosure deadlines for Project Zero’s issues were extended by Google:
- CVE-2016-7613 -- “task_t considered harmful”, 145 days
- Multiple CVEs -- “Spectre and Meltdown”, 216 days
- CVE-2020-1027 -- “In the Wild Series: Windows Exploits”, 23 days (actively exploited issue under a 7-day deadline)
- CVE-2020-27930 -- “In-the-Wild Series: October 2020 0-day discovery”, 101 days (actively exploited issue under a 7-day deadline)
- CVE-2020-27932 -- “In-the-Wild Series: October 2020 0-day discovery”, 98 days (actively exploited issue under a 7-day deadline)
- CVE-2020-27950 -- “In-the-Wild Series: October 2020 0-day discovery”, 98 days (actively exploited issue under a 7-day deadline)
- CVE-2023-24033 -- “Multiple Internet to Baseband Remote Code Execution Vulnerabilities in Exynos Modems”, 174 days
- CVE-2023-26496 -- “Multiple Internet to Baseband Remote Code Execution Vulnerabilities in Exynos Modems”, 136 days
- CVE-2023-26497 -- “Multiple Internet to Baseband Remote Code Execution Vulnerabilities in Exynos Modems”, 136 days
- CVE-2023-26498 -- “Multiple Internet to Baseband Remote Code Execution Vulnerabilities in Exynos Modems”, 136 days
How do you decide who to report a vulnerability to?🔗
We report vulnerabilities directly to the vendor or open source project that is responsible for developing the fix. Generally we use the official point of contact for security bug reports (e.g., an email address or issue tracker) and we follow each project’s documented process for handling security bugs until the disclosure deadline has passed.
We also share the Project Zero reference number, vendor, product, report date and disclosure deadline for all vulnerabilities we report on a weekly basis on our Reporting Transparency page.
Sometimes we get asked to share our vulnerability reports with third parties, such as organizations that are affected by the vulnerability. We decline these requests, and encourage these parties to instead contact the upstream vendor. Project Zero accounts for only a portion of vulnerabilities reported to most software makers, and we feel that relying on vulnerability reporters to share information is not an effective approach for downstream patch propagation, and has substantial downsides, including increased risk of leaks and inconsistency in patch delivery. In the long term, we hope our policy will help to facilitate better coordination between upstream and downstream parties that need to ship fixes.
What do you do if a vendor says a bug is invalid, or says that they cannot, or will not, fix it?🔗
If we report an issue and the vendor indicates that they won’t be issuing a patch, then we derestrict the technical details in our issue tracker (i.e., make the issue publicly available for discussion) with a status of WontFix and include an additional technical assessment of the developer’s response.
In essence, we shift from treating the bug report as a vulnerability (where the rules of vulnerability disclosure apply) and instead treat the issue as a non-security bug (where there are typically no restrictions on public discussion). We think this incentivizes vendors to perform high-quality triaging of our bug reports, and we’ve seen a significant improvement in the quality of the triage we receive in response to this approach.
When the Project Zero disclosure policy changes, what policy applies to bugs that have already been reported?🔗
Vulnerabilities we report are subject to the disclosure policy on the date they were reported. The policy that applies to a specific vulnerability can be found in the text at the bottom of the report.
Does Google have early access to Project Zero’s detailed technical vulnerability reports?🔗
Typically only Project Zero team members (who are Google employees) and a small number of security engineers working inside the team on “20% projects” have access to Project Zero’s vulnerability reports prior to public disclosure. An obvious exception is when Google is the recipient of our reports: when we discover vulnerabilities in Chrome, Android, and other Google-supported software, we follow Google’s standard external bug reporting procedures, the same processes that a non-Google security researcher would experience. We recommend that vendors follow their usual downstream notification processes for vulnerabilities we report, including notifying teams at Google, as we do not share vulnerability reports internally.