Heap corruption via FedCM use-after-free
Published Mar 6, 2024 · Updated Feb 13, 2025
A use-after-free in FedCM in Google Chrome before 122.0.6261.111 allows remote attackers to corrupt heap memory via a crafted HTML page. Google identifies the FedCM component but has not published the freed object, lifetime error, or stale access that causes the heap corruption. Exploitation requires a user to open the page; the public record does not establish whether the resulting corruption produces a crash or code execution.
Summary
What happened
A use-after-free in FedCM in Google Chrome before 122.0.6261.111 allows remote attackers to corrupt heap memory via a crafted HTML page. Google identifies the FedCM component but has not published the freed object, lifetime error, or stale access that causes the heap corruption. Exploitation requires a user to open the page; the public record does not establish whether the resulting corruption produces a crash or code execution.
The record
- CVE
- CVE-2024-2176
- Published
- Mar 6, 2024
- Updated
- Feb 13, 2025
- Vendor
- Fedora Project
- Product
- Fedora Linux
- Classifications
- CWE-416, T1189
- 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.
Public exploit references
- Chromium issue 325936438 proof of conceptproof of concept · unverified
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