Code execution via browser memory corruption
Published Mar 19, 2024 · Updated Mar 14, 2025
Memory corruption in Mozilla Firefox before 124 allows remote attackers to execute arbitrary code through malicious web content. TitleChangeEvent::Run dereferences a freed Document, while DeviceInfoPipeWire::CreateCapabilityMap copies a device ID using the display-name length. DOM activity reaches the title-event defect, while the PipeWire camera path is disabled by default; successful corruption executes code in the browser process.
Summary
What happened
Memory corruption in Mozilla Firefox before 124 allows remote attackers to execute arbitrary code through malicious web content. TitleChangeEvent::Run dereferences a freed Document, while DeviceInfoPipeWire::CreateCapabilityMap copies a device ID using the display-name length. DOM activity reaches the title-event defect, while the PipeWire camera path is disabled by default; successful corruption executes code in the browser process.
The record
- CVE
- CVE-2024-2615
- Published
- Mar 19, 2024
- Updated
- Mar 14, 2025
- Vendor
- Mozilla
- Product
- Firefox
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 19, 2024CVE publishedPublication date reported by the CVE source.
- Mar 14, 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 <124
- Affected versionversion=unspecified <124
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
- Bug 1881074 testcase.htmlproof of concept · demonstrated
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