Vulnerabilities / Threats

2/9/2018
02:06 PM
Connect Directly
Twitter
LinkedIn
Google+
RSS
E-Mail
50%
50%

Google Paid $2.9M for Vulnerabilities in 2017

The Google Vulnerability Reward Program issued a total of 1,230 rewards in 2017. The single largest payout was $112,500.

Google issued a total of $2.9 million in 2017 as part of its Google Vulnerability Reward Program, which has so far paid out $12 million since it was first created in November 2010.

More than $1 million was given for vulnerabilities discovered and reported in Google products, and $1.1 million was given for Android bugs. Google reports it gave out 1,230 individual rewards and 274 paid researchers were involved in the program last year.

The Vulnerability Research Grants program awarded $125,000 to more than 50 security researchers around the world. This initiative, a complement to the Vulnerability Reward Program, pays researchers and invited experts to investigate the security of Google products and services, even in situations where no vulnerabilities are discovered.

Its Patch Rewards Program, an experimental program founded in 2013 which rewards proactive security improvements to open-source projects, paid $50,000 to participants in 2017.

The largest individual reward from last year amounted to $112,500, which was also the highest-ever bug bounty paid for an Android flaw. It went to researcher Guang Gong, from the Alpha Team at Qihoo 360 Technology, who submitted the first working remote exploit chain since the Android Security Rewards (ASR) program expanded in June 2017.

Gong's exploit chain contained two bugs. CVE-2017-5116 is a V8 engine bug used to get remote code execution in the sandboxed Chrome render process. CVE-2017-14904 is a flaw in Android libgralloc module used to escape Chrome's sandbox. Combined, the chain can be leveraged to inject arbitrary code into system_server by accessing a malicious URL in Chrome.

Also worth noting is researcher "gzobqq," who earned the $100,000 pwnium award for a chain of bugs across five components, which achieved remote code execution in guest mode on the Chrome OS. Researcher Alex Birsan was paid $15,600 in bounties for discovering anyone could have gained access to internal Google Issue Tracker data.

Google is bumping up the highest reward for a remote exploit chain, or exploit leading to TrustZone or Verified Boot compromise, from $50,000 to $200,000. It has also increased the top reward for a remote kernel exploit from $30,000 to $150,000. The range of rewards for remote code executions runs from $1,000 to $5,000 per bug.

Related Content:

 

Black Hat Asia returns to Singapore with hands-on technical Trainings, cutting-edge Briefings, Arsenal open-source tool demonstrations, top-tier solutions and service providers in the Business Hall. Click for information on the conference and to register.

Kelly Sheridan is the Staff Editor at Dark Reading, where she focuses on cybersecurity news and analysis. She is a business technology journalist who previously reported for InformationWeek, where she covered Microsoft, and Insurance & Technology, where she covered financial ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Want Your Daughter to Succeed in Cyber? Call Her John
John De Santis, CEO, HyTrust,  5/16/2018
Don't Roll the Dice When Prioritizing Vulnerability Fixes
Ericka Chickowski, Contributing Writer, Dark Reading,  5/15/2018
New Mexico Man Sentenced on DDoS, Gun Charges
Dark Reading Staff 5/18/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: "Security through obscurity"
Current Issue
Flash Poll
[Strategic Security Report] Navigating the Threat Intelligence Maze
[Strategic Security Report] Navigating the Threat Intelligence Maze
Most enterprises are using threat intel services, but many are still figuring out how to use the data they're collecting. In this Dark Reading survey we give you a look at what they're doing today - and where they hope to go.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2017-2607
PUBLISHED: 2018-05-21
jenkins before versions 2.44, 2.32.2 is vulnerable to a persisted cross-site scripting vulnerability in console notes (SECURITY-382). Jenkins allows plugins to annotate build logs, adding new content or changing the presentation of existing content while the build is running. Malicious Jenkins users...
CVE-2018-1108
PUBLISHED: 2018-05-21
kernel drivers before version 4.17-rc1 are vulnerable to a weakness in the Linux kernel's implementation of random seed data. Programs, early in the boot sequence, could use the data allocated for the seed before it was sufficiently generated.
CVE-2018-11330
PUBLISHED: 2018-05-21
An issue was discovered in Pluck before 4.7.6. There is authenticated stored XSS because the character set for filenames is not properly restricted.
CVE-2018-11331
PUBLISHED: 2018-05-21
An issue was discovered in Pluck before 4.7.6. Remote PHP code execution is possible because the set of disallowed filetypes for uploads in missing some applicable ones such as .phtml and .htaccess.
CVE-2018-7687
PUBLISHED: 2018-05-21
The Micro Focus Client for OES before version 2 SP4 IR8a has a vulnerability that could allow a local attacker to elevate privileges via a buffer overflow in ncfsd.sys.