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

11/8/2019
02:00 PM
Connect Directly
Twitter
LinkedIn
RSS
E-Mail
100%
0%

Bugcrowd Pays Out Over $500K in Bounties in One Week

In all, bug hunters from around the world submitted over 6,500 vulnerabilities in October alone.

Crowdsourced bug disclosure programs are popular. The latest evidence is Bugcrowd, which in October alone paid out $1.6 million to some 550 white hat hackers from around the world who collectively reported a total of 6,500 vulnerabilities in products belonging to companies signed up with the platform.

More than $513,000 of those payouts was made just last week—a record in a 7-day period for Bugcrowd since it launched in 2011. The biggest payout of $40,000 went to a hacker who disclosed a bug in an automotive software product.

Over 300 of the 6,500 valid bug submissions to Bugcrowd in October were classified as P1 under Bugcrowd's vulnerability rating taxonomy. These are bugs that are most critical in nature.

Examples include privilege escalation bugs, remote code execution flaws, and bugs that enable financial theft or expose critically sensitive data such as passwords, says David Baker, CSO and vice president of operations at Bugcrowd. "Some recognizable examples of a P1 vulnerability are EternalBlue, BlueKeep, and Apache Struts, the vulnerability that led to the massive breach at Equifax."

Bugcrowd's numbers for October are considerably higher than five years ago, when it paid about $30,000 to 85 hackers. Just five of the bugs reported in October in 2014 were critical.

According to Bugcrowd, bug bounty payouts for 2019 so far is more than 80% higher than last year's payouts, meaning that security researchers are finding and reporting a lot more bugs than ever under the program. "In a matter of a five-year span, we’ve exponentially multiplied payouts, Crowd engagement, and critical findings," Bugcrowd said in a statement Friday. "To say we’re excited is an understatement."

Managed vulnerability hunting and disclosure programs like Bugcrowd, HackerOne, and Synack have become popular in recent years. Many organizations—across industries and companies of all sizes—have signed up with these platforms and let freelance bug hunters poke and prod at their products for security vulnerabilities. The goal is to give organizations a way to find bugs in their software that they might have otherwise missed—and more cheaply than if they were to hire their own security researchers for the job.

As is to be expected a majority of the bugs that security researchers find and report to Bugcrowd are of the medium to low severity type, Baker says. "As a rule, there's always going to be fewer critical issues than there are medium- or low-severity findings—simply by the fact that they're harder to find," he notes. "That said, the most dollars have gone out for medium-priority findings, compared to high or critical vulnerabilities," he notes.

On average, bug submissions on Bugcrowd can fetch around $900. But high-severity and critical P1 bugs can garner around $3,000 on average and much more in some cases. "Car hacking skill tends to be a pretty lucrative skillset," for instance, Baker says.

Since launch, security researchers have reported over 300,000 vulnerabilities to the Bugcrowd platform. Over the last year alone, submissions increased nearly two-fold, Baker says. Currently, hundreds of thousands of security researchers from around the world are signed up with the platform.

About 30% of them are from the United States. India hosts the second largest group, followed by Great Britain, Baker says. Over the last couple of years, crowdsourced security activity has really accelerated in India, he says. "We are seeing not just an increase in researchers but also a gradual increase in skills as people learn from and teach others."

Related Content:

Check out The Edge, Dark Reading's new section for features, threat data, and in-depth perspectives. Today's top story: "What a Security Products Blacklist Means for End Users and Integrators."

Jai Vijayan is a seasoned technology reporter with over 20 years of experience in IT trade journalism. He was most recently a Senior Editor at Computerworld, where he covered information security and data privacy issues for the publication. Over the course of his 20-year ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Oldest First  |  Newest First  |  Threaded View
Data Leak Week: Billions of Sensitive Files Exposed Online
Kelly Jackson Higgins, Executive Editor at Dark Reading,  12/10/2019
Lessons from the NSA: Know Your Assets
Robert Lemos, Contributing Writer,  12/12/2019
4 Tips to Run Fast in the Face of Digital Transformation
Shane Buckley, President & Chief Operating Officer, Gigamon,  12/9/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
The Year in Security: 2019
This Tech Digest provides a wrap up and overview of the year's top cybersecurity news stories. It was a year of new twists on old threats, with fears of another WannaCry-type worm and of a possible botnet army of Wi-Fi routers. But 2019 also underscored the risk of firmware and trusted security tools harboring dangerous holes that cybercriminals and nation-state hackers could readily abuse. Read more.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-19807
PUBLISHED: 2019-12-15
In the Linux kernel before 5.3.11, sound/core/timer.c has a use-after-free caused by erroneous code refactoring, aka CID-e7af6307a8a5. This is related to snd_timer_open and snd_timer_close_locked. The timeri variable was originally intended to be for a newly created timer instance, but was used for ...
CVE-2014-8650
PUBLISHED: 2019-12-15
python-requests-Kerberos through 0.5 does not handle mutual authentication
CVE-2014-3536
PUBLISHED: 2019-12-15
CFME (CloudForms Management Engine) 5: RHN account information is logged to top_output.log during registration
CVE-2014-3643
PUBLISHED: 2019-12-15
jersey: XXE via parameter entities not disabled by the jersey SAX parser
CVE-2014-3652
PUBLISHED: 2019-12-15
JBoss KeyCloak: Open redirect vulnerability via failure to validate the redirect URL.