Sandbox escape via dangling FileWriter callback
Published Jan 2, 2023 · Updated Oct 23, 2024
Use-after-free in Google Chrome's FileAPI before 72.0.3626.81 allows remote attackers to escape the browser sandbox via crafted HTML. FileWriterImpl::Write binds DoWrite through an unchecked, unowned object pointer, while a renderer-controlled Blob callback can destroy the FileWriter before DoWrite runs. Exploitation requires user interaction and a separate renderer compromise; successful use grants code execution outside the renderer sandbox.
Summary
What happened
Use-after-free in Google Chrome's FileAPI before 72.0.3626.81 allows remote attackers to escape the browser sandbox via crafted HTML. FileWriterImpl::Write binds DoWrite through an unchecked, unowned object pointer, while a renderer-controlled Blob callback can destroy the FileWriter before DoWrite runs. Exploitation requires user interaction and a separate renderer compromise; successful use grants code execution outside the renderer sandbox.
The record
- CVE
- CVE-2019-13768
- Published
- Jan 2, 2023
- Updated
- Oct 23, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416, T1068
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 2, 2023CVE publishedPublication date reported by the CVE source.
- Oct 23, 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 <72.0.3626.81
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
- Full chain Chrome 71.0.3578.98 exploitfunctional · demonstrated
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