Security

Rock Chrome hard enough and get paid half a million

Google revises Chrome Vulnerability Rewards Program with higher payouts for bug hunters


Google's Chrome Vulnerability Rewards Program (VRP) is now significantly more rewarding – with a top payout that's at least twice as substantial.

Citing the challenge of finding consequential, exploitable bugs in its Chrome browser after 16 years in release, Amy Ressler, information security engineer at the Chocolate Factory, explained it was time to rethink Chrome VRP rewards to incentivize higher quality bug reporting and deeper research into Chrome vulnerabilities.

Google's approach, according to Ressler, reflects a move away from a list of specific rewards that has separated memory corruption issues from other classes of vulnerabilities. For the past few years, memory safety has become an industry and government priority because the majority of meaningful bugs in large C++ codebases like Chrome are down to flaws like use-after-free and buffer overflows.

Google's new reward structure for memory corruption bugs focuses on four vulnerability categories: high-quality report with demonstration of remote code execution (RCE); high-quality report demonstrating controlled write to an arbitrary memory location; high-quality report of memory corruption; and a baseline report consisting of a stack trace and proof-of-concept exploit code.

"While the reward amounts for baseline reports of memory corruption will remain consistent, we have increased reward amounts in the other categories with the goal of incentivizing deeper research into the full consequences of a given issue," said Ressler. "The highest potential reward amount for a single issue is now $250,000 for demonstrated RCE in a non-sandboxed process."

And obtaining RCE in a non-sandboxed process without a renderer compromise qualifies for a higher amount, to capture the renderer RCE reward.

Other classes of vulnerabilities, for a high-quality report on a high-impact bug, top out at $30,000 for a UXSS/site isolation bypass.

Then there's the award for bypassing MiraclePtr – a mechanism to protect against use-after-free memory corruption. Basically, it implements a reference counter that blocks the reuse of freed/released memory when positive and frees it upon reaching zero.

The launch of MiraclePtr in Chrome's active release channels last year meant that bugs mitigated by MiraclePtr in non-renderer processes were considered to be substantially mitigated. But being able to bypass MiraclePtr protection was deemed worthy of a special reward in the amount of $100,115.

With the arrival of Chrome 128, Ressler says that MiraclePtr-protected bugs in non-renderer processes aren't even worth considering as security bugs. So now Google considers MiraclePtr a declarative security boundary and is thus eligible for a reward that reflects the seriousness of crossing that line: $250,128.

So per Google's documentation, a new use-after-free memory corruption bug that demonstrates a MiraclePtr bypass with a high-impact, functional exploit and a high-quality writeup could net $500,128.

Get hunting. ®

Send us news
Post a comment

Chrome dumped support for Ubuntu 18.04 – but it'll be back

Complaints about lack of notice plus an inquiry from El Reg prompt U-turn by web giant

Digital wallets can allow purchases with stolen credit cards

Researchers find it's possible to downgrade authentication checks, and shabby token refresh policies

Yelp accuses Google of being a local search bully in antitrust lawsuit

Chocolate Factory claims rival is trying to revive cases it's already lost

Rust for Linux maintainer steps down in frustration with 'nontechnical nonsense'

Community seems to C Rust more as a burden than a benefit

GPT apps fail to disclose data collection, study finds

Researchers say that implementing Actions omit privacy details and expose info

Top companies ground Microsoft Copilot over data governance concerns

Securiti's Jack Berkowitz polled 20-plus CDOs, and half have hit pause

Google is a monopoly. The fix isn't obvious

A business breakup may be coming – but what comes after may not be better

Alleged Karakut ransomware scumbag charged in US

Plus: Microsoft issues workaround for dual-boot crashes; ARRL cops to ransom payment, and more

Deadline looms: Google Workspace mandates OAuth by September 30

27 days to get your users' third-party apps on Google’s sign-in

This uni thought it would be a good idea to do a phishing test with a fake Ebola scare

Needless to say, it backfired in a big way

Microsoft security tools questioned for treating employees as threats

Cracked Labs examines how workplace surveillance turns workers into suspects

Microsoft hosts a security summit but no press, public allowed

CrowdStrike, other vendors, friendly govt reps…but not anyone who would tell you what happened