Sandbox escape via Blink heap buffer overflow
Published Jul 28, 2023 · Updated Feb 13, 2025
Heap buffer overflow in Blink in Google Chrome before 101.0.4951.41 allows remote attackers to escape the sandbox via crafted HTML. Google has not published the affected Blink code locus or the specific operation that writes beyond the heap buffer. Exploitation requires convincing a user to open the page and perform specific UI gestures; successful exploitation crosses the renderer sandbox boundary.
Summary
What happened
Heap buffer overflow in Blink in Google Chrome before 101.0.4951.41 allows remote attackers to escape the sandbox via crafted HTML. Google has not published the affected Blink code locus or the specific operation that writes beyond the heap buffer. Exploitation requires convincing a user to open the page and perform specific UI gestures; successful exploitation crosses the renderer sandbox boundary.
The record
- CVE
- CVE-2022-4920
- Published
- Jul 28, 2023
- Updated
- Feb 13, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 28, 2023CVE publishedPublication date reported by the CVE source.
- Feb 13, 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=0 <101.0.4951.41
- Affected versionversion=101.0.4951.41 <101.0.4951.41
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