Memory disclosure via V8 out-of-bounds read
Published Jul 16, 2024 · Updated Mar 19, 2025
Out-of-bounds read in V8 in Google Chrome before 121.0.6167.139 allows remote attackers to read memory via a crafted HTML page. Public records identify V8 as the locus but do not disclose the affected function, input field, or missing bounds check because the Chromium issue requires sign-in. A user must load attacker-controlled HTML; published impact is limited to memory disclosure, with no reported write or code execution.
Summary
What happened
Out-of-bounds read in V8 in Google Chrome before 121.0.6167.139 allows remote attackers to read memory via a crafted HTML page. Public records identify V8 as the locus but do not disclose the affected function, input field, or missing bounds check because the Chromium issue requires sign-in. A user must load attacker-controlled HTML; published impact is limited to memory disclosure, with no reported write or code execution.
The record
- CVE
- CVE-2024-2884
- Published
- Jul 16, 2024
- Updated
- Mar 19, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-125
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 16, 2024CVE publishedPublication date reported by the CVE source.
- Mar 19, 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.139 <121.0.6167.139
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