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.

Risk //


12:59 AM

Coordinated Disclosure, Bug Bounties Help Speed Patches

Vulnerability advisories are increasingly accompanied by a patch these days, indicating that researchers and software firms are working more closely

For more than a decade, researchers and software makers have debated the proper method of disclosing vulnerabilities so that end users might be best protected against the malicious exploitation of the security holes.

A recent report suggests that the current combination of coordinated disclosure, where researchers work with companies to allow them time to fix vulnerabilities, as well as bounty programs that pay researchers who find vulnerabilities has shortened the time between publication and patch. In its Vulnerability Review 2013, security firm Secunia found that the gap between the vulnerabilities patched within a day of publication and within a month of publication had narrowed considerably, for the top-50 software programs on end-user systems. In 2012, more than 80 percent of vulnerabilities in those applications had a patch distributed within a day of the advisory being published, compared to slightly more than 60 percent in 2007.

The dramatic increase shows the evolving maturity of researchers and software makers alike, says Kasper Lindgaard, research manager with Secunia.

"As I see it, the vendors are doing a good deal of work to make it easer for researchers to coordinate their vulnerabilities," Lindgaard says. "Some years ago, it was much harder than it is now."

More software vendors are creating product security teams to handle vulnerability reports and to communicate with researchers. While Microsoft, Google, Facebook, and Adobe have well-known product security teams, smaller companies have started to adopt the process, he says.

A decade ago, initial positions on disclosure tended toward extremes: Either researchers fully disclosed the details of a vulnerability--ostensibly to shame the vendor into improving their security--or the researchers worked with the software maker to help close the security hole and did not disclose the issue without permission.

In 2000, security researcher and consultant Jeff Forristal--known only as "Rain Forest Puppy" at the time--created the first draft of RFPolicy to codify a more moderate process to ensure that vulnerabilities are fixed before they are disclosed. However, the policy also allowed the researcher to unilaterally release details of the flaw, if the software vendor did not give regular updates or release a patch for the issue in a reasonable time.

Since the first publication of the policy, researchers and software vendors have come up with other schemes, such as partial disclosure, responsible disclosure, and the withholding of details of the vulnerability for profit.

[To protect against a cyber attacker, you have to think like a cyber attacker. The reason so many attacks are reasonably straightforward is that most attackers use exploit toolkits downloaded from the Internet. See How Attackers Choose Which Vulnerabilities To Exploit.]

The privatization of vulnerabilities has taken many forms--from white market programs, such as Hewlett-Packard's Zero Day Initiative to Google's Pwnium bounty for bugs found in Chrome, to programs that exist in a far more gray area, such as VUPEN Security and Immunity, who sell to private clients and penetration testers. This private market for vulnerabilities helps security, says Brian Gorenc, the manager of the Zero Day Initiative at HP Security Research.

"You are seeing the majority of the privatization market trying to get the vulnerabilities patched in a timely manner," Gorenc says. "And the bugs that are kept private are eventually going to be found by other researchers."

Yet patching the software flaws is only one half of the security equation, argues HD Moore, chief security officer at vulnerability management firm Rapid7. While the vulnerabilities are being patched, the time between when a software company receives a report of a security issue and when it patches the flaw is getting longer, says Moore. While some may argue that getting 100 percent of vulnerabilities patched at the time disclosure is a laudable goal, software companies would again become complacent, he says.

"Because so many folks are playing along with the vendors, we are seeing a much slower process to fix software than we would see otherwise," he says. "Yet, that 20 percent is enough of a stick out there that it helps the folks who are willing to work with the vendors get taken much more seriously."

Have a comment on this story? Please click "Add Your Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message. Veteran technology journalist of more than 20 years. Former research engineer. Written for more than two dozen publications, including CNET News.com, Dark Reading, MIT's Technology Review, Popular Science, and Wired News. Five awards for journalism, including Best Deadline ... View Full Bio

Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/25/2020
WannaCry Has IoT in Its Crosshairs
Ed Koehler, Distinguished Principal Security Engineer, Office of CTO, at Extreme Network,  9/25/2020
Safeguarding Schools Against RDP-Based Ransomware
James Lui, Ericom Group CTO, Americas,  9/28/2020
Register for Dark Reading Newsletters
White Papers
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
New Best Practices for Secure App Development
New Best Practices for Secure App Development
The transition from DevOps to SecDevOps is combining with the move toward cloud computing to create new challenges - and new opportunities - for the information security team. Download this report, to learn about the new best practices for secure application development.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2020-09-27
XSS exists in the MobileFrontend extension for MediaWiki before 1.34.4 because section.line is mishandled during regex section line replacement from PageGateway. Using crafted HTML, an attacker can elicit an XSS attack via jQuery's parseHTML method, which can cause image callbacks to fire even witho...
PUBLISHED: 2020-09-27
An issue was discovered in the FileImporter extension for MediaWiki before 1.34.4. An attacker can import a file even when the target page is protected against "page creation" and the attacker should not be able to create it. This occurs because of a mishandled distinction between an uploa...
PUBLISHED: 2020-09-27
An issue was discovered in MediaWiki 1.34.x before 1.34.4. On Special:Contributions, the NS filter uses unescaped messages as keys in the option key for an HTMLForm specifier. This is vulnerable to a mild XSS if one of those messages is changed to include raw HTML.
PUBLISHED: 2020-09-27
In MediaWiki before 1.31.10 and 1.32.x through 1.34.x before 1.34.4, Special:UserRights exposes the existence of hidden users.
PUBLISHED: 2020-09-27
In MediaWiki before 1.31.10 and 1.32.x through 1.34.x before 1.34.4, XSS related to jQuery can occur. The attacker creates a message with [javascript:payload xss] and turns it into a jQuery object with mw.message().parse(). The expected result is that the jQuery object does not contain an <a> ...