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.

Vulnerabilities / Threats

7/11/2013
11:13 AM
50%
50%

Overcome The Microsoft Mindset: Patch Faster

Why can't vendors patch every critical bug like it was the Pwn2Own competition?

9 Android Apps To Improve Security, Privacy
9 Android Apps To Improve Security, Privacy
(click image for larger view)
Software vendors: Prepare to adjust your patching reality.

The long-running debate about how fast software vendors should be required to squash bugs in their products is heating up again, following Microsoft's release on July 9 of a fix for a critical bug that had been detailed publicly by Google security researcher Tavis Ormandy seven weeks prior. Microsoft said the bug had already been exploited in "targeted attacks."

Who's right and wrong in this scenario? Ormandy, for releasing full details of a bug and a working exploit, without giving Microsoft a courtesy call and time to code a fix? Or Microsoft, for dictating the terms of the game and generally giving itself lots of time to fix bugs that aren't being actively exploited?

[ How did a hacker hijack the Emergency Alert System? Read 'Zombie Apocalypse' Broadcast Hoax Explained. ]

Regardless of your take, Google seems set to rewrite the rules of the bug-patching game, after two of its security researchers, Chris Evans and Drew Hintz, issued a warning to vendors in a May blog post: In cases of "critical vulnerabilities under active exploitation," Google will now give vendors only seven days to release a patch. After that time, Google will issue full details of the vulnerability. For anything that's not critical, Google is sticking with its recommendation to fix bugs within 60 days or else issue workarounds and mitigation techniques to affected users.

While acknowledging that the seven-day timeline is "aggressive," Evans and Hintz said everyone stands to benefit. "By holding ourselves to the same standard, we hope to improve both the state of Web security and the coordination of vulnerability management," they said in their post.

Google's revised bug-disclosure timeline is good news for all software users. "It shows that the long timeframes that the industry has been operating under -- find a vulnerability, ensure it's fixed within six months or a year -- isn't adequate," SANS Institute fellow Ed Skoudis told me in a phone interview. "So Google is trying to juice the whole thing to make it happen faster."

Skoudis added: "Microsoft got us into this mindset: You find a flaw, responsibly tell a vendor, and darn it, there will be a fix out within a year."

The annual Pwn2Own competition, hosted by Hewlett-Packard's DVLabs Zero Day Initiative (ZDI), has also been reshaping our collective patching mindset. "Google and Mozilla were able to patch the issues that were being exploited in the competition in less than two days," said ZDI manager Brian Gorenc, speaking by phone. Of course, it was in both companies' best interests to patch their browsers quickly, thus making Chrome and Firefox look better than Internet Explorer. "For actively exploited bugs, they pose an immediate problem for vendors, and they need to be pressured to act quickly," Gorenc said.

Previous
1 of 2
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
MartinRH
50%
50%
MartinRH,
User Rank: Apprentice
7/14/2013 | 5:25:54 AM
re: Overcome The Microsoft Mindset: Patch Faster
Great piece Mathew. It will be interesting and useful to see if and/or how this pans out. "go git 'em Google!" ;-)
COVID-19: Latest Security News & Commentary
Dark Reading Staff 11/19/2020
New Proposed DNS Security Features Released
Kelly Jackson Higgins, Executive Editor at Dark Reading,  11/19/2020
How to Identify Cobalt Strike on Your Network
Zohar Buber, Security Analyst,  11/18/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-25159
PUBLISHED: 2020-11-24
499ES EtherNet/IP (ENIP) Adaptor Source Code is vulnerable to a stack-based buffer overflow, which may allow an attacker to send a specially crafted packet that may result in a denial-of-service condition or code execution.
CVE-2020-25654
PUBLISHED: 2020-11-24
An ACL bypass flaw was found in pacemaker before 1.1.24-rc1 and 2.0.5-rc2. An attacker having a local account on the cluster and in the haclient group could use IPC communication with various daemons directly to perform certain tasks that they would be prevented by ACLs from doing if they went throu...
CVE-2020-28329
PUBLISHED: 2020-11-24
Barco wePresent WiPG-1600W firmware includes a hardcoded API account and password that is discoverable by inspecting the firmware image. A malicious actor could use this password to access authenticated, administrative functions in the API. Affected Version(s): 2.5.1.8, 2.5.0.25, 2.5.0.24, 2.4.1.19.
CVE-2020-29053
PUBLISHED: 2020-11-24
HRSALE 2.0.0 allows XSS via the admin/project/projects_calendar set_date parameter.
CVE-2020-25640
PUBLISHED: 2020-11-24
A flaw was discovered in WildFly before 21.0.0.Final where, Resource adapter logs plain text JMS password at warning level on connection error, inserting sensitive information in the log file.