Heap corruption via WebGL out-of-bounds access
Published Aug 3, 2023 · Updated Feb 13, 2025
Out-of-bounds memory access in Google Chrome WebGL before 115.0.5790.170 allows remote attackers to corrupt the heap via crafted HTML. WebGL processing reads and writes beyond an allocated buffer when handling attacker-controlled page content; the exact function and faulty bounds calculation remain undisclosed. Exploitation requires a user to load the crafted page, and successful heap corruption can compromise browser data, execution integrity, or availability.
Summary
What happened
Out-of-bounds memory access in Google Chrome WebGL before 115.0.5790.170 allows remote attackers to corrupt the heap via crafted HTML. WebGL processing reads and writes beyond an allocated buffer when handling attacker-controlled page content; the exact function and faulty bounds calculation remain undisclosed. Exploitation requires a user to load the crafted page, and successful heap corruption can compromise browser data, execution integrity, or availability.
The record
- CVE
- CVE-2023-4072
- Published
- Aug 3, 2023
- Updated
- Feb 13, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-125, CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 3, 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=115.0.5790.170 <115.0.5790.170
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.
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