Browser crash via ambiguous PHC realloc failure
Published Jun 11, 2024 · Updated Oct 30, 2024
Memory corruption in Firefox before 127 allows remote attackers to crash the browser through crafted content under low-memory conditions. MaybePageRealloc uses null for both a handled PHC allocation failure and an unhandled allocation, causing PageRealloc to pass a PHC pointer to mozjemalloc. Corruption requires attacker-influenced PHC allocations in specific positions; the usual consequence is a browser crash.
Summary
What happened
Memory corruption in Firefox before 127 allows remote attackers to crash the browser through crafted content under low-memory conditions. MaybePageRealloc uses null for both a handled PHC allocation failure and an unhandled allocation, causing PageRealloc to pass a PHC pointer to mozjemalloc. Corruption requires attacker-influenced PHC allocations in specific positions; the usual consequence is a browser crash.
The record
- CVE
- CVE-2024-5695
- Published
- Jun 11, 2024
- Updated
- Oct 30, 2024
- Vendor
- Mozilla
- Product
- Firefox
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 11, 2024CVE publishedPublication date reported by the CVE source.
- Oct 30, 2024Record 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 <127
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.
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