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
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/25/2020
Hacking Yourself: Marie Moe and Pacemaker Security
Gary McGraw Ph.D., Co-founder Berryville Institute of Machine Learning,  9/21/2020
Startup Aims to Map and Track All the IT and Security Things
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
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
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15208
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, when determining the common dimension size of two tensors, TFLite uses a `DCHECK` which is no-op outside of debug compilation modes. Since the function always returns the dimension of the first tensor, malicious attackers can ...
CVE-2020-15209
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, a crafted TFLite model can force a node to have as input a tensor backed by a `nullptr` buffer. This can be achieved by changing a buffer index in the flatbuffer serialization to convert a read-only tensor to a read-write one....
CVE-2020-15210
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, if a TFLite saved model uses the same tensor as both input and output of an operator, then, depending on the operator, we can observe a segmentation fault or just memory corruption. We have patched the issue in d58c96946b and ...
CVE-2020-15211
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, saved models in the flatbuffer format use a double indexing scheme: a model has a set of subgraphs, each subgraph has a set of operators and each operator has a set of input/output tensors. The flatbuffer format uses indices f...
CVE-2020-15212
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger writes outside of bounds of heap allocated buffers by inserting negative elements in the segment ids tensor. Users having access to `segment_ids_data` can alter `output_index` and then write to outside of `outpu...