Browser crash via improper certificate validation
Published Jan 21, 2020 · Updated Aug 6, 2024
Improper certificate validation in Mozilla Firefox before 3.6 allows remote attackers to crash the browser via a crafted certificate. Public records do not identify the validation routine or explain which certificate property it handles incorrectly. A user must be induced to process the certificate; the documented consequence is an availability-only browser crash.
Summary
What happened
Improper certificate validation in Mozilla Firefox before 3.6 allows remote attackers to crash the browser via a crafted certificate. Public records do not identify the validation routine or explain which certificate property it handles incorrectly. A user must be induced to process the certificate; the documented consequence is an availability-only browser crash.
The record
- CVE
- CVE-2011-2669
- Published
- Jan 21, 2020
- Updated
- Aug 6, 2024
- Vendor
- Mozilla
- Product
- Firefox
- Classifications
- CWE-295, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 21, 2020CVE publishedPublication date reported by the CVE source.
- Aug 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=prior to 3.6
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