Code execution via undisclosed memory corruption
Published Jun 24, 2021 · Updated Aug 3, 2024
Memory corruption in Mozilla Firefox before 89 allows remote attackers to execute arbitrary code after a user opens malicious web content. Mozilla groups four memory-safety defects under this identifier but does not disclose the affected components or invalid memory operations. Exploitation requires user interaction and can compromise the Firefox process; no server-side exposure is indicated.
Summary
What happened
Memory corruption in Mozilla Firefox before 89 allows remote attackers to execute arbitrary code after a user opens malicious web content. Mozilla groups four memory-safety defects under this identifier but does not disclose the affected components or invalid memory operations. Exploitation requires user interaction and can compromise the Firefox process; no server-side exposure is indicated.
The record
- CVE
- CVE-2021-29966
- Published
- Jun 24, 2021
- Updated
- Aug 3, 2024
- Vendor
- Mozilla
- Product
- Firefox
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 24, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record 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 <89
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