Arbitrary code execution via memory corruption
Published May 14, 2024 · Updated Mar 13, 2025
Memory-safety flaws in Mozilla Firefox before 126, Firefox ESR before 115.11, and Thunderbird before 115.11 allow code execution. Mozilla identified evidence of memory corruption across two underlying bugs but has not publicly disclosed the affected code loci or erroneous memory operations. Exploitation requires remote delivery of crafted client-side content and user interaction; successful execution occurs in the application context.
Summary
What happened
Memory-safety flaws in Mozilla Firefox before 126, Firefox ESR before 115.11, and Thunderbird before 115.11 allow code execution. Mozilla identified evidence of memory corruption across two underlying bugs but has not publicly disclosed the affected code loci or erroneous memory operations. Exploitation requires remote delivery of crafted client-side content and user interaction; successful execution occurs in the application context.
The record
- CVE
- CVE-2024-4777
- Published
- May 14, 2024
- Updated
- Mar 13, 2025
- Vendor
- Mozilla
- Product
- Firefox
- Classifications
- CWE-120, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 14, 2024CVE publishedPublication date reported by the CVE source.
- Mar 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=0 <126
- Affected versionversion=unspecified <126
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.
Weakness, pattern, technique
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