Application crash via stale WeakRef tracking
Published Oct 24, 2023 · Updated Feb 13, 2025
Improper object tracking in Firefox before 119, Firefox ESR before 115.4, and Thunderbird before 115.4.1 allows remote attackers to crash. When a WeakRef target is cleared, FinalizationObservers leaves its cross-compartment wrapper in weakRefMap, so a later garbage-collection validity check encounters a dead wrapper. Triggering requires crafted JavaScript that manipulates cross-compartment WeakRef targets; the demonstrated consequence is a segmentation-fault crash.
Summary
What happened
Improper object tracking in Firefox before 119, Firefox ESR before 115.4, and Thunderbird before 115.4.1 allows remote attackers to crash. When a WeakRef target is cleared, FinalizationObservers leaves its cross-compartment wrapper in weakRefMap, so a later garbage-collection validity check encounters a dead wrapper. Triggering requires crafted JavaScript that manipulates cross-compartment WeakRef targets; the demonstrated consequence is a segmentation-fault crash.
The record
- CVE
- CVE-2023-5728
- Published
- Oct 24, 2023
- Updated
- Feb 13, 2025
- Vendor
- Mozilla
- Product
- Firefox
- Classifications
- CWE-416, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 24, 2023CVE 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=unspecified <119
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