Arbitrary code execution via memory corruption
Published Sep 3, 2024 · Updated Sep 6, 2024
Memory-safety bugs in Mozilla Firefox before 130 allow remote attackers to execute arbitrary code through network-delivered input. Mozilla has not disclosed the affected components or invalid memory operations that caused corruption in the two referenced bugs. No authentication or user interaction is required, and successful memory corruption enables code execution in the browser process.
Summary
What happened
Memory-safety bugs in Mozilla Firefox before 130 allow remote attackers to execute arbitrary code through network-delivered input. Mozilla has not disclosed the affected components or invalid memory operations that caused corruption in the two referenced bugs. No authentication or user interaction is required, and successful memory corruption enables code execution in the browser process.
The record
- CVE
- CVE-2024-8389
- Published
- Sep 3, 2024
- Updated
- Sep 6, 2024
- Vendor
- Mozilla
- Product
- Firefox
- Classifications
- CWE-787, CWE-119, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 3, 2024CVE publishedPublication date reported by the CVE source.
- Sep 6, 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=0 <130
- Affected versionversion=unspecified <130
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