Heap corruption via Network use after free
Published Jan 30, 2024 · Updated Jun 3, 2025
Use after free in Google Chrome's Network component before 121.0.6167.139 allows remote attackers to corrupt heap memory via a malicious file. Public vendor material identifies stale-object access in Network but does not disclose the affected object, code path, or lifetime error that frees it too early. Exploitation requires user interaction with the malicious file and can compromise confidentiality, integrity, and availability.
Summary
What happened
Use after free in Google Chrome's Network component before 121.0.6167.139 allows remote attackers to corrupt heap memory via a malicious file. Public vendor material identifies stale-object access in Network but does not disclose the affected object, code path, or lifetime error that frees it too early. Exploitation requires user interaction with the malicious file and can compromise confidentiality, integrity, and availability.
The record
- CVE
- CVE-2024-1077
- Published
- Jan 30, 2024
- Updated
- Jun 3, 2025
- Vendor
- Fedora Project
- Product
- Fedora Linux
- Classifications
- CWE-416, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 30, 2024CVE publishedPublication date reported by the CVE source.
- Jun 3, 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=38
- Affected versionversion=39
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