Sandbox escape via task-scheduling use-after-free
Published May 21, 2020 · Updated Aug 4, 2024
Use-after-free in Google Chrome before 81.0.4044.129 allows remote attackers with a compromised renderer to escape its sandbox. Google identifies task scheduling as the affected component but has not published the freed object, lifetime error, or triggering operation. A crafted HTML page and prior renderer compromise are required; successful exploitation crosses the browser sandbox and reaches the host context.
Summary
What happened
Use-after-free in Google Chrome before 81.0.4044.129 allows remote attackers with a compromised renderer to escape its sandbox. Google identifies task scheduling as the affected component but has not published the freed object, lifetime error, or triggering operation. A crafted HTML page and prior renderer compromise are required; successful exploitation crosses the browser sandbox and reaches the host context.
The record
- CVE
- CVE-2020-6462
- Published
- May 21, 2020
- Updated
- Aug 4, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 21, 2020CVE 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 <81.0.4044.129
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