Arbitrary code execution via memory corruption
Published Dec 22, 2022 · Updated Apr 15, 2025
Memory-safety flaws in Mozilla Firefox before 106 allow remote attackers to execute arbitrary code through crafted web content. Mozilla identified four underlying defects that corrupt memory but did not disclose the affected functions or exact invalid memory operations. Exploitation requires a user to load attacker-controlled content, and successful code runs within the browser's security context.
Summary
What happened
Memory-safety flaws in Mozilla Firefox before 106 allow remote attackers to execute arbitrary code through crafted web content. Mozilla identified four underlying defects that corrupt memory but did not disclose the affected functions or exact invalid memory operations. Exploitation requires a user to load attacker-controlled content, and successful code runs within the browser's security context.
The record
- CVE
- CVE-2022-46885
- Published
- Dec 22, 2022
- Updated
- Apr 15, 2025
- Vendor
- Mozilla
- Product
- Firefox
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 22, 2022CVE publishedPublication date reported by the CVE source.
- Apr 15, 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 <106
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
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