Remote code execution from memory corruption
Published Nov 21, 2023 · Updated Feb 13, 2025
Memory-safety defects in Mozilla Firefox before 120 allow remote attackers to execute code through crafted web content. Mozilla links three underlying bugs but has not disclosed their affected code loci or the invalid memory operations; testing showed memory corruption. A user must load attacker-controlled content, and successful exploitation can run code in the browser security context.
Summary
What happened
Memory-safety defects in Mozilla Firefox before 120 allow remote attackers to execute code through crafted web content. Mozilla links three underlying bugs but has not disclosed their affected code loci or the invalid memory operations; testing showed memory corruption. A user must load attacker-controlled content, and successful exploitation can run code in the browser security context.
The record
- CVE
- CVE-2023-6213
- Published
- Nov 21, 2023
- Updated
- Feb 13, 2025
- Vendor
- Mozilla
- Product
- Firefox
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 21, 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 <120
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