Arbitrary code execution via memory corruption
Published Dec 22, 2022 · Updated Apr 15, 2025
Memory safety flaws in Mozilla Firefox before 103 allow remote attackers to execute arbitrary code through attacker-controlled content. Mozilla reports multiple bugs showing memory corruption but does not disclose the affected code paths or erroneous operations for this CVE. No authentication or local access is required; successful exploitation executes code in the browser's security context.
Summary
What happened
Memory safety flaws in Mozilla Firefox before 103 allow remote attackers to execute arbitrary code through attacker-controlled content. Mozilla reports multiple bugs showing memory corruption but does not disclose the affected code paths or erroneous operations for this CVE. No authentication or local access is required; successful exploitation executes code in the browser's security context.
The record
- CVE
- CVE-2022-36320
- 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 <103
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