Sandbox escape via stale PaymentCredential callback
Published Jan 8, 2021 · Updated Aug 4, 2024
Use-after-free in Google Chrome payments before 87.0.4280.66 allows remote attackers with a compromised renderer to escape the sandbox. The PaymentCredential::DidDownloadFavicon path passes its object as a raw callback pointer, while creation of another binding can destroy that object before the callback runs. A crafted HTML page must first compromise the renderer; successful reuse of the freed browser-side object crosses the renderer sandbox boundary.
Summary
What happened
Use-after-free in Google Chrome payments before 87.0.4280.66 allows remote attackers with a compromised renderer to escape the sandbox. The PaymentCredential::DidDownloadFavicon path passes its object as a raw callback pointer, while creation of another binding can destroy that object before the callback runs. A crafted HTML page must first compromise the renderer; successful reuse of the freed browser-side object crosses the renderer sandbox boundary.
The record
- CVE
- CVE-2020-16018
- Published
- Jan 8, 2021
- Updated
- Aug 4, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416, T1068
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 8, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <87.0.4280.66
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo