Process-memory disclosure via V8 type confusion
Published Jul 26, 2022 · Updated Aug 3, 2024
Type confusion in V8 in Google Chrome before 101.0.4951.41 allows remote attackers to read potentially sensitive process memory via crafted HTML. Google identifies the locus as V8 but has not published the confused types or the incorrect operation that exposes process memory. Exploitation requires a user to open attacker-controlled HTML, and the reported consequence is limited to disclosure from the browser process.
Summary
What happened
Type confusion in V8 in Google Chrome before 101.0.4951.41 allows remote attackers to read potentially sensitive process memory via crafted HTML. Google identifies the locus as V8 but has not published the confused types or the incorrect operation that exposes process memory. Exploitation requires a user to open attacker-controlled HTML, and the reported consequence is limited to disclosure from the browser process.
The record
- CVE
- CVE-2022-1486
- Published
- Jul 26, 2022
- Updated
- Aug 3, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-843, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 26, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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 <101.0.4951.41
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