Heap corruption via V8 type confusion
Published Jul 16, 2024 · Updated Oct 15, 2024
Type confusion in V8 in Google Chrome before 126.0.6478.182 allows remote attackers to trigger heap corruption through a crafted HTML page. Google identifies V8 as the affected component but has not published the erroneous type operation because the underlying issue details remain restricted. Exploitation requires a user to load attacker-controlled content and can compromise the browser process; a sandbox escape is not established.
Summary
What happened
Type confusion in V8 in Google Chrome before 126.0.6478.182 allows remote attackers to trigger heap corruption through a crafted HTML page. Google identifies V8 as the affected component but has not published the erroneous type operation because the underlying issue details remain restricted. Exploitation requires a user to load attacker-controlled content and can compromise the browser process; a sandbox escape is not established.
The record
- CVE
- CVE-2024-6773
- Published
- Jul 16, 2024
- Updated
- Oct 15, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- T1203, T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 16, 2024CVE publishedPublication date reported by the CVE source.
- Oct 15, 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=0 <126.0.6478.182
- Affected versionversion=126.0.6478.182 <126.0.6478.182
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