Code execution via memory corruption
Published Mar 31, 2021 · Updated Aug 3, 2024
Memory safety bugs in Mozilla Firefox 86 allow remote attackers to trigger memory corruption through attacker-controlled web content. Mozilla has not published the specific code locus or malformed input responsible for the corruption. Exploitation requires a victim to open attacker-controlled content; successful corruption could permit arbitrary code execution, but no specific exploit is reported.
Summary
What happened
Memory safety bugs in Mozilla Firefox 86 allow remote attackers to trigger memory corruption through attacker-controlled web content. Mozilla has not published the specific code locus or malformed input responsible for the corruption. Exploitation requires a victim to open attacker-controlled content; successful corruption could permit arbitrary code execution, but no specific exploit is reported.
The record
- CVE
- CVE-2021-23988
- Published
- Mar 31, 2021
- Updated
- Aug 3, 2024
- Vendor
- Mozilla
- Product
- Firefox
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 31, 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 <87
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