Arbitrary code execution via undisclosed memory corruption
Published Jun 2, 2023 · Updated Jan 8, 2025
Memory corruption in Mozilla Firefox before 111 allows remote attackers to execute arbitrary code after user interaction with web content. Mozilla groups four memory-safety defects under this identifier but does not publicly identify the faulty routines or the unsafe operations they perform. A victim must interact with attacker-controlled web content, and successful exploitation runs code with the Firefox process's privileges.
Summary
What happened
Memory corruption in Mozilla Firefox before 111 allows remote attackers to execute arbitrary code after user interaction with web content. Mozilla groups four memory-safety defects under this identifier but does not publicly identify the faulty routines or the unsafe operations they perform. A victim must interact with attacker-controlled web content, and successful exploitation runs code with the Firefox process's privileges.
The record
- CVE
- CVE-2023-28177
- Published
- Jun 2, 2023
- Updated
- Jan 8, 2025
- Vendor
- Mozilla
- Product
- Firefox
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 2, 2023CVE publishedPublication date reported by the CVE source.
- Jan 8, 2025Record 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 <111
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