Sandbox escape via logging use-after-free
Published Nov 1, 2022 · Updated May 6, 2025
Use-after-free in Google Chrome logging before 106.0.5249.62 allows remote attackers to escape the sandbox through crafted HTML. The logging component accesses an object after its storage has been freed, but Google has not disclosed the affected function or lifetime transition. Exploitation requires user interaction and prior compromise of a WebUI process; the published impact is unauthorized modification beyond the sandbox boundary.
Summary
What happened
Use-after-free in Google Chrome logging before 106.0.5249.62 allows remote attackers to escape the sandbox through crafted HTML. The logging component accesses an object after its storage has been freed, but Google has not disclosed the affected function or lifetime transition. Exploitation requires user interaction and prior compromise of a WebUI process; the published impact is unauthorized modification beyond the sandbox boundary.
The record
- CVE
- CVE-2022-3314
- Published
- Nov 1, 2022
- Updated
- May 6, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 1, 2022CVE publishedPublication date reported by the CVE source.
- May 6, 2025Record 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 <106.0.5249.62
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