Code execution via memory corruption bugs
Published Jan 8, 2020 · Updated Aug 5, 2024
Memory safety flaws in Mozilla Firefox before 71 allow remote attackers to execute code through malicious web content. The rollup covers use-after-free conditions and out-of-bounds writes across browser components, where stale objects or unchecked writes corrupt memory. A victim must load attacker-controlled content; successful exploitation runs code in the browser context and can crash the Firefox process.
Summary
What happened
Memory safety flaws in Mozilla Firefox before 71 allow remote attackers to execute code through malicious web content. The rollup covers use-after-free conditions and out-of-bounds writes across browser components, where stale objects or unchecked writes corrupt memory. A victim must load attacker-controlled content; successful exploitation runs code in the browser context and can crash the Firefox process.
The record
- CVE
- CVE-2019-17013
- Published
- Jan 8, 2020
- Updated
- Aug 5, 2024
- Vendor
- Mozilla
- Product
- Firefox
- Classifications
- CWE-416, CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 8, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 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=before 71
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.
Weakness, pattern, technique
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