Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Application Security

1/8/2020
03:25 PM
100%
0%

Google's Project Zero Policy Change Mandates 90-Day Disclosure

The updated disclosure policy aims to achieve more thorough and improved patch development, Google reports.

Google's Project Zero, a division focused on security research, today announced changes to its Disclosure Policy. All vulnerabilities will be released after 90 days by default regardless of when a bug is fixed, unless an agreement has been made between Project Zero and the vendor.

The 90-day disclosure deadline has existed for five years and accelerated patch development. When Project Zero began in 2014, some vulnerabilities took longer than six months to address. Last year, 97.7% of issues were addressed under the 90-day deadline. Still, the division recognizes there is progress to be made in patch development and vulnerability management.

Now it is trialing a new policy for bugs reported starting January 1, 2020. Project Zero's old guidelines allowed vulnerability details to be released when the bug was fixed, even if it was ahead of Day 90. Its new policy eliminates early disclosure: details will be released on Day 90 for all bugs. If there is mutual agreement between the vendor and Project Zero, bug reports can be released to the public under the 90-day timeline, researchers report in a blog post.

The goal is to provide a more consistent, and fair way to release patches, wrote Project Zero's Tim Willis in a blog post. While faster patch development remains a goal, the team is now placing equal focus on thorough patch development and broad adoption. It also hopes to create equity among vendors so no one company, including Google, gets preferential treatment.

"Too many times, we've seen vendors patch reported vulnerabilities by 'papering over the cracks' and not considering variants or addressing the root cause of a vulnerability," Willis explained. A focus on "faster patch development" may exacerbate this issue, he continued, enabling attackers to adjust their exploits and continue launching attacks.

Further, Willis pointed out, patches must be applied in order to be effective. "To this end, improving timely patch adoption is important to ensure that users are actually acquiring the benefit from the bug being fixed." With the mandated 90-day window, the hope is that vendors should be able to offer updates and encourage more people to install fixes within 90 days.

Project Zero will test this policy for 12 months then consider whether to make it a long-term change. Read more details in the full blog post here.

Check out The Edge, Dark Reading's new section for features, threat data, and in-depth perspectives. Today's top story: "Car Hacking Hits the Streets"

Dark Reading's Quick Hits delivers a brief synopsis and summary of the significance of breaking news events. For more information from the original source of the news item, please follow the link provided in this article. View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
RuskinF
50%
50%
RuskinF,
User Rank: Apprentice
1/9/2020 | 7:28:35 AM
90 days to release the disclosure
Google resolving 97.7% issues within 90 days is a great thing. Now they need to improve their efficiency just by a bit, making the figure 99%. It is challenging but not impossible.
Zero-Factor Authentication: Owning Our Data
Nick Selby, Chief Security Officer at Paxos Trust Company,  2/19/2020
44% of Security Threats Start in the Cloud
Kelly Sheridan, Staff Editor, Dark Reading,  2/19/2020
Ransomware Damage Hit $11.5B in 2019
Dark Reading Staff 2/20/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
6 Emerging Cyber Threats That Enterprises Face in 2020
This Tech Digest gives an in-depth look at six emerging cyber threats that enterprises could face in 2020. Download your copy today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-7914
PUBLISHED: 2020-02-21
btif/src/btif_dm.c in Android before 5.1 does not properly enforce the temporary nature of a Bluetooth pairing, which allows user-assisted remote attackers to bypass intended access restrictions via crafted Bluetooth packets after the tapping of a crafted NFC tag.
CVE-2016-4606
PUBLISHED: 2020-02-21
Curl before 7.49.1 in Apple OS X before macOS Sierra prior to 10.12 allows remote or local attackers to execute arbitrary code, gain sensitive information, cause denial-of-service conditions, bypass security restrictions, and perform unauthorized actions. This may aid in other attacks.
CVE-2020-5243
PUBLISHED: 2020-02-21
uap-core before 0.7.3 is vulnerable to a denial of service attack when processing crafted User-Agent strings. Some regexes are vulnerable to regular expression denial of service (REDoS) due to overlapping capture groups. This allows remote attackers to overload a server by setting the User-Agent hea...
CVE-2019-14688
PUBLISHED: 2020-02-20
Trend Micro has repackaged installers for several Trend Micro products that were found to utilize a version of an install package that had a DLL hijack vulnerability that could be exploited during a new product installation. The vulnerability was found to ONLY be exploitable during an initial produc...
CVE-2019-19694
PUBLISHED: 2020-02-20
The Trend Micro Security 2019 (15.0.0.1163 and below) consumer family of products is vulnerable to a denial of service (DoS) attack in which a malicious actor could manipulate a key file at a certain time during the system startup process to disable the product's malware protection functions or the ...