Sandbox escape via Web Transport use-after-free
Published Nov 23, 2021 · Updated Aug 4, 2024
Use-after-free in Google Chrome Web Transport before 95.0.4638.69 allows remote attackers to escape the sandbox via crafted HTML. The Web Transport implementation accesses an object after its memory has been freed, but public records do not identify the affected function or object. Exploitation requires a user to load attacker-controlled HTML, and successful exploitation crosses the browser sandbox boundary.
Summary
What happened
Use-after-free in Google Chrome Web Transport before 95.0.4638.69 allows remote attackers to escape the sandbox via crafted HTML. The Web Transport implementation accesses an object after its memory has been freed, but public records do not identify the affected function or object. Exploitation requires a user to load attacker-controlled HTML, and successful exploitation crosses the browser sandbox boundary.
The record
- CVE
- CVE-2021-38002
- Published
- Nov 23, 2021
- Updated
- Aug 4, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 23, 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 <95.0.4638.69
What conditions does exploitation require?
What is affected?
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