Heap corruption via Mojo use-after-free
Published Feb 21, 2024 · Updated Feb 13, 2025
Use-after-free in Google Chrome before 122.0.6261.57 allows remote attackers to corrupt heap memory through a crafted HTML page. The public record identifies only the Mojo component and does not disclose the object, call path, or operation that retains the freed reference. Exploitation requires user interaction with attacker-controlled HTML and can compromise confidentiality, integrity, and availability in the browser context.
Summary
What happened
Use-after-free in Google Chrome before 122.0.6261.57 allows remote attackers to corrupt heap memory through a crafted HTML page. The public record identifies only the Mojo component and does not disclose the object, call path, or operation that retains the freed reference. Exploitation requires user interaction with attacker-controlled HTML and can compromise confidentiality, integrity, and availability in the browser context.
The record
- CVE
- CVE-2024-1670
- Published
- Feb 21, 2024
- Updated
- Feb 13, 2025
- Vendor
- Fedora Project
- Product
- Fedora Linux
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 21, 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=39
- 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.
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