Remote code execution via memory corruption
Published May 26, 2020 · Updated Aug 4, 2024
Memory corruption in Mozilla Firefox before 76, Firefox ESR before 68.8, and Thunderbird before 68.8.0 allows remote attackers to execute code. Mozilla groups multiple memory-safety defects under this identifier but does not disclose the individual code loci or erroneous operations. Exploitation requires attacker-controlled browser or browser-like content; Thunderbird email reading disables scripting, limiting that path.
Summary
What happened
Memory corruption in Mozilla Firefox before 76, Firefox ESR before 68.8, and Thunderbird before 68.8.0 allows remote attackers to execute code. Mozilla groups multiple memory-safety defects under this identifier but does not disclose the individual code loci or erroneous operations. Exploitation requires attacker-controlled browser or browser-like content; Thunderbird email reading disables scripting, limiting that path.
The record
- CVE
- CVE-2020-12395
- Published
- May 26, 2020
- Updated
- Aug 4, 2024
- Vendor
- Mozilla
- Product
- Firefox
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 26, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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 <76
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