Arbitrary code execution via memory safety bugs
Published Apr 24, 2020 · Updated Aug 4, 2024
Memory safety vulnerability in Mozilla Firefox 74 allows remote attackers to execute arbitrary code via unspecified vectors. Mozilla reports memory-safety bugs with evidence of memory corruption but does not disclose a specific component, operation, or trigger. The advisory does not establish authentication, user interaction, or a safely reproducible runtime condition beyond exploitation of affected browser code.
Summary
What happened
Memory safety vulnerability in Mozilla Firefox 74 allows remote attackers to execute arbitrary code via unspecified vectors. Mozilla reports memory-safety bugs with evidence of memory corruption but does not disclose a specific component, operation, or trigger. The advisory does not establish authentication, user interaction, or a safely reproducible runtime condition beyond exploitation of affected browser code.
The record
- CVE
- CVE-2020-6826
- Published
- Apr 24, 2020
- Updated
- Aug 4, 2024
- Vendor
- Mozilla
- Product
- Firefox
- Classifications
- Unavailable
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 24, 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 <75
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
No sourced classifications are available.
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