Heap corruption via ANGLE buffer overflow
Published Jan 4, 2024 · Updated Jun 18, 2025
Heap buffer overflow in ANGLE in Google Chrome before 120.0.6099.199 allows remote attackers to corrupt heap memory via crafted HTML. Google's public bulletin identifies ANGLE but leaves the affected routine and the incorrect bounds or allocation operation undisclosed because the linked issue remains restricted. A browser user must load the crafted page; public sources do not establish a resulting browser crash, code execution, or sandbox escape.
Summary
What happened
Heap buffer overflow in ANGLE in Google Chrome before 120.0.6099.199 allows remote attackers to corrupt heap memory via crafted HTML. Google's public bulletin identifies ANGLE but leaves the affected routine and the incorrect bounds or allocation operation undisclosed because the linked issue remains restricted. A browser user must load the crafted page; public sources do not establish a resulting browser crash, code execution, or sandbox escape.
The record
- CVE
- CVE-2024-0223
- Published
- Jan 4, 2024
- Updated
- Jun 18, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 4, 2024CVE publishedPublication date reported by the CVE source.
- Jun 18, 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=120.0.6099.199 <120.0.6099.199
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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.
Weakness, pattern, technique
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