Browser object corruption via crafted HTML
Published Mar 20, 2024 · Updated Mar 13, 2025
Object lifecycle corruption in V8 in Google Chrome before 123.0.6312.58 allows remote attackers to corrupt browser objects via crafted HTML. Google and Chromium have not publicly disclosed the faulty V8 operation or object type, and the linked issue remains access-restricted. A user must load the crafted page; the published record establishes object corruption but does not disclose whether exploitation stops at a crash or gains code execution.
Summary
What happened
Object lifecycle corruption in V8 in Google Chrome before 123.0.6312.58 allows remote attackers to corrupt browser objects via crafted HTML. Google and Chromium have not publicly disclosed the faulty V8 operation or object type, and the linked issue remains access-restricted. A user must load the crafted page; the published record establishes object corruption but does not disclose whether exploitation stops at a crash or gains code execution.
The record
- CVE
- CVE-2024-2625
- Published
- Mar 20, 2024
- Updated
- Mar 13, 2025
- Vendor
- Fedora Project
- Product
- Fedora Linux
- Classifications
- T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 20, 2024CVE publishedPublication date reported by the CVE source.
- Mar 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=39
- Affected versionversion=40
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