Heap corruption via V8 out-of-bounds memory access
Published Apr 5, 2022 · Updated Aug 2, 2024
Out-of-bounds memory access in Google Chrome before 98.0.4758.80 allows remote attackers to corrupt the V8 heap via crafted HTML. The V8 engine accesses memory outside an intended boundary while processing the page, but Google has not disclosed the responsible function or incorrect bounds operation. A victim must open the page; the disclosed consequence is heap corruption, while resulting reads, writes, or control-flow effects are unspecified.
Summary
What happened
Out-of-bounds memory access in Google Chrome before 98.0.4758.80 allows remote attackers to corrupt the V8 heap via crafted HTML. The V8 engine accesses memory outside an intended boundary while processing the page, but Google has not disclosed the responsible function or incorrect bounds operation. A victim must open the page; the disclosed consequence is heap corruption, while resulting reads, writes, or control-flow effects are unspecified.
The record
- CVE
- CVE-2022-0470
- Published
- Apr 5, 2022
- Updated
- Aug 2, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-787, T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 5, 2022CVE publishedPublication date reported by the CVE source.
- Aug 2, 2024Record 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=unspecified <98.0.4758.80
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