Vulnerabilities / Threats

1/19/2018
12:00 PM
100%
0%

Google Pays Researcher Record $112,500 for Android Flaw

The bug bounty reward, given to a researcher who submitted a working remote exploit chain, is Google's highest for an Android bug.

Google has awarded its highest-ever bug bounty for an Android flaw, the company announced this week. The $112,500 reward was paid to a researcher who submitted the first working remote exploit chain since the Android Security Rewards (ASR) program expanded in June 2017.

Guang Gong, from the Alpha Team at Qihoo 360 Technology, submitted his report in August. The exploit chain he found includes two bugs: CVE-2017-5116 and CVE-2017-14904. The first is a V8 engine bug used to get remote code execution in the sandboxed Chrome render process. The second, a bug in Android's libgralloc module, is used to escape from Chrome's sandbox.

Together, the exploit chain can be used to inject arbitrary code into system_server by accessing a malicious URL in Chrome. Gong's findings earned him $105,000 from ASR, the highest reward in the history of the program. He was also given $7,500 from the Chrome Rewards program.

The full set of issues Gong discovered was addressed in the December 2017 monthly security update, and all devices with security patches of 2017-12-05 or later are protected. Pixel devices and partner devices using A/B updates will automatically install the fixes when restarted.

Read more details here.

Dark Reading's Quick Hits delivers a brief synopsis and summary of the significance of breaking news events. For more information from the original source of the news item, please follow the link provided in this article. View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Oldest First  |  Newest First  |  Threaded View
MariaColeman
50%
50%
MariaColeman,
User Rank: Apprentice
1/23/2018 | 11:55:15 AM
Why so much?
But for what? I can't understand( 
High Stress Levels Impacting CISOs Physically, Mentally
Jai Vijayan, Freelance writer,  2/14/2019
Valentine's Emails Laced with Gandcrab Ransomware
Kelly Sheridan, Staff Editor, Dark Reading,  2/14/2019
Making the Case for a Cybersecurity Moon Shot
Adam Shostack, Consultant, Entrepreneur, Technologist, Game Designer,  2/19/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
5 Emerging Cyber Threats to Watch for in 2019
Online attackers are constantly developing new, innovative ways to break into the enterprise. This Dark Reading Tech Digest gives an in-depth look at five emerging attack trends and exploits your security team should look out for, along with helpful recommendations on how you can prevent your organization from falling victim.
Flash Poll
How Enterprises Are Attacking the Cybersecurity Problem
How Enterprises Are Attacking the Cybersecurity Problem
Data breach fears and the need to comply with regulations such as GDPR are two major drivers increased spending on security products and technologies. But other factors are contributing to the trend as well. Find out more about how enterprises are attacking the cybersecurity problem by reading our report today.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-8980
PUBLISHED: 2019-02-21
A memory leak in the kernel_read_file function in fs/exec.c in the Linux kernel through 4.20.11 allows attackers to cause a denial of service (memory consumption) by triggering vfs_read failures.
CVE-2019-8979
PUBLISHED: 2019-02-21
Koseven through 3.3.9, and Kohana through 3.3.6, has SQL Injection when the order_by() parameter can be controlled.
CVE-2013-7469
PUBLISHED: 2019-02-21
Seafile through 6.2.11 always uses the same Initialization Vector (IV) with Cipher Block Chaining (CBC) Mode to encrypt private data, making it easier to conduct chosen-plaintext attacks or dictionary attacks.
CVE-2018-20146
PUBLISHED: 2019-02-21
An issue was discovered in Liquidware ProfileUnity before 6.8.0 with Liquidware FlexApp before 6.8.0. A local user could obtain administrator rights, as demonstrated by use of PowerShell.
CVE-2019-5727
PUBLISHED: 2019-02-21
Splunk Web in Splunk Enterprise 6.5.x before 6.5.5, 6.4.x before 6.4.9, 6.3.x before 6.3.12, 6.2.x before 6.2.14, 6.1.x before 6.1.14, and 6.0.x before 6.0.15 and Splunk Light before 6.6.0 has Persistent XSS, aka SPL-138827.