CVE-2018-9127
Last modified
CVE-2018-9127 is a vulnerability of currently unknown severity. Botan 2.2.0 - 2.4.0 (fixed in 2.5.0) improperly handled wildcard certificates and could accept certain certificates as valid for hostnames when, under RFC 6125 rules, they should not match. This only affects certificates issued to the same domain as the host, so to impersonate a host one must already have a wildcard certificate matching other hosts in the same domain. EPSS estimates a 0.96% chance of exploitation in the next 30 days.
Description
Botan 2.2.0 - 2.4.0 (fixed in 2.5.0) improperly handled wildcard certificates and could accept certain certificates as valid for hostnames when, under RFC 6125 rules, they should not match. This only affects certificates issued to the same domain as the host, so to impersonate a host one must already have a wildcard certificate matching other hosts in the same domain. For example, b*.example.com would match some hostnames that do not begin with a 'b' character.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Botan Project | Botan | >= 2.2.0, <= 2.4.0 |
References
- https://botan.randombit.net/security.htmlThird Party Advisory
- https://botan.randombit.net/security.htmlThird Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2018-9127?
How severe is CVE-2018-9127?
How do I fix CVE-2018-9127?
Are you affected by CVE-2018-9127?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST