CVE-2024-3853
High · 7.5CVSS
7.5
EPSS
0.4%
Published
Apr 16, 2024
CISA due date
—
Cloudanix analysis
A memory handling error in the browser could let a malicious website take over a user's computer.
- Exploitation
- Adjacent Network
- Attacker needs
- None
- Complexity
- High
- Impact
- Full Compromise
- Component
- Application
- Class
- Use After Free
- Remediation
- Upgrade
- Effort
- Medium
- Patch risk
- Low
What it actually does
Use-after-free condition triggered when a JavaScript realm initializes concurrently with garbage collection, allowing memory corruption.
Why it matters to the business
Attackers could execute arbitrary code or crash the browser on affected systems, risking data theft, malware installation, or loss of user sessions.
How an attack unfolds
An attacker hosts a malicious web page that forces concurrent JavaScript realm initialization and garbage collection to trigger the use-after-free and achieve code execution.
How to fix it
Upgrade affected Firefox installations to version 125 or later; apply the listed fixed package versions for any impacted Alpine vim packages.
How to confirm the fix worked
Verify browser version is 125 or higher; confirm package versions match the fixed releases for Alpine vim components.
Typical attack path
- Deliver malicious JavaScript via a crafted webpage
- Trigger simultaneous realm initialization and garbage collection
- Exploit the resulting use-after-free for memory corruption
- Achieve arbitrary code execution in the browser process
How to detect it
Review browser crash logs and memory dumps for signs of use-after-free patterns; inspect web request logs for suspicious JavaScript activity.
What your security team should do
- Prioritize immediate browser updates across all endpoints
- Monitor for unusual browser crashes or memory-related alerts
- Block access to untrusted websites until patches are deployed
The record
A use-after-free could result if a JavaScript realm was in the process of being initialized when a garbage collection started. This vulnerability affects Firefox < 125.
Affected packages
| Ecosystem | Package | Introduced | Fixed |
|---|---|---|---|
| Ubuntu:18.04:LTS | mozjs38 | 0 | No fix |
| Ubuntu:18.04:LTS | mozjs52 | 0 | No fix |
| Ubuntu:20.04:LTS | firefox | 0 | 125.0.2+build1-0ubuntu0.20.04.2 |
| Ubuntu:20.04:LTS | mozjs52 | 0 | No fix |
| Ubuntu:20.04:LTS | mozjs68 | 0 | No fix |
| Ubuntu:22.04:LTS | mozjs102 | 0 | No fix |
| Ubuntu:22.04:LTS | mozjs78 | 0 | No fix |
| Ubuntu:22.04:LTS | mozjs91 | 0 | No fix |
| Ubuntu:24.04:LTS | mozjs102 | 0 | No fix |
| Ubuntu:Pro:18.04:LTS | mozjs38 | 0 | No fix |
| Ubuntu:Pro:18.04:LTS | mozjs52 | 0 | No fix |
| Ubuntu:Pro:20.04:LTS | mozjs52 | 0 | No fix |
| Ubuntu:Pro:20.04:LTS | mozjs68 | 0 | No fix |
| Ubuntu:Pro:22.04:LTS | mozjs78 | 0 | No fix |
| Ubuntu:Pro:24.04:LTS | mozjs102 | 0 | No fix |
| openSUSE:Tumbleweed | MozillaFirefox | 0 | 125.0.2-1.1 |
| openSUSE:Tumbleweed | firefox-esr | 0 | 128.5.1-1.1 |
Related vulnerabilities
- CVE-2025-0243 Memory safety bugs present in Firefox 133, Thunderbird 133, Firefox ESR 128.5, and… Also affects mozjs38
- CVE-2025-0237 The WebChannel API, which is used to transport various information across processes, did… Also affects mozjs38
- CVE-2025-0238 Assuming a controlled failed memory allocation, an attacker could have caused a… Also affects mozjs38
- CVE-2025-0240 Parsing a JavaScript module as JSON could, under some circumstances, cause… Also affects mozjs38
- CVE-2025-0239 When using Alt-Svc, ALPN did not properly validate certificates when the original server… Also affects mozjs38
- CVE-2025-0241 When segmenting specially crafted text, segmentation would corrupt memory leading to a… Also affects mozjs38
- CVE-2025-0242 Memory safety bugs present in Firefox 133, Thunderbird 133, Firefox ESR 115.18, Firefox… Also affects mozjs38
- CVE-2024-11704 A double-free issue could have occurred in `sec_pkcs7_decoder_start_decrypt()` when… Also affects mozjs38