Heap corruption via V8 out-of-bounds access
Published Jan 15, 2025 · Updated Mar 14, 2025
Out-of-bounds memory access in V8 in Google Chrome before 132.0.6834.83 allows remote attackers to corrupt heap memory via crafted HTML. Google identifies V8 as the locus but keeps the technical issue restricted, so the exact operation that crosses the memory boundary is undisclosed. The required gate is a user loading attacker-controlled HTML; successful exploitation corrupts heap memory within Chrome's sandbox.
Summary
What happened
Out-of-bounds memory access in V8 in Google Chrome before 132.0.6834.83 allows remote attackers to corrupt heap memory via crafted HTML. Google identifies V8 as the locus but keeps the technical issue restricted, so the exact operation that crosses the memory boundary is undisclosed. The required gate is a user loading attacker-controlled HTML; successful exploitation corrupts heap memory within Chrome's sandbox.
The record
- CVE
- CVE-2025-0434
- Published
- Jan 15, 2025
- Updated
- Mar 14, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-122, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 15, 2025CVE publishedPublication date reported by the CVE source.
- Mar 14, 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=132.0.6834.83 <132.0.6834.83
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.
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