Code execution via undisclosed V8 implementation flaw
Published Mar 6, 2024 · Updated Feb 13, 2025
Heap corruption in V8 in Google Chrome before 122.0.6261.111 allows remote attackers to execute code via a crafted HTML page. Google has not published the faulty V8 operation; the public record identifies only an inappropriate implementation that corrupts heap memory. Exposure requires a user to load attacker-controlled HTML, and Fedora Linux 40 is also listed as affected.
Summary
What happened
Heap corruption in V8 in Google Chrome before 122.0.6261.111 allows remote attackers to execute code via a crafted HTML page. Google has not published the faulty V8 operation; the public record identifies only an inappropriate implementation that corrupts heap memory. Exposure requires a user to load attacker-controlled HTML, and Fedora Linux 40 is also listed as affected.
The record
- CVE
- CVE-2024-2174
- Published
- Mar 6, 2024
- Updated
- Feb 13, 2025
- Vendor
- Fedora Project
- Product
- Fedora Linux
- Classifications
- CWE-787, CWE-358, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 6, 2024CVE publishedPublication date reported by the CVE source.
- Feb 13, 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=40
What conditions does exploitation require?
What is affected?
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