Heap corruption via WebUI integer underflow
Published Jan 23, 2024 · Updated May 30, 2025
Integer underflow in WebUI in Google Chrome before 121.0.6167.85 allows remote attackers to corrupt heap memory via a malicious file. Google identifies the locus as WebUI, but the restricted issue record does not disclose which arithmetic operation underflows or how file data reaches it. A crafted file must reach the browser; public vendor material establishes heap corruption but does not establish code execution, a crash, or data access.
Summary
What happened
Integer underflow in WebUI in Google Chrome before 121.0.6167.85 allows remote attackers to corrupt heap memory via a malicious file. Google identifies the locus as WebUI, but the restricted issue record does not disclose which arithmetic operation underflows or how file data reaches it. A crafted file must reach the browser; public vendor material establishes heap corruption but does not establish code execution, a crash, or data access.
The record
- CVE
- CVE-2024-0808
- Published
- Jan 23, 2024
- Updated
- May 30, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-191
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 23, 2024CVE publishedPublication date reported by the CVE source.
- May 30, 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=121.0.6167.85 <121.0.6167.85
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