CVE intelligence and bounded remediation
CVE-2018-9127 — Botan Project Botan security vulnerability
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.
- Severity
- Critical
- CVSS
- 9.8 (3.0)
- Published
- 2018-04-02
- CISA KEV
- Not currently listed
- Ecosystem
- software/application
- Weaknesses
- CWE-295
Affected products
- botan_project / botan
Matched remediation archetype
Cryptography, certificate, signature, and channel validation
This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.
Check exposure
- Inventory affected algorithms, key uses, trust stores, certificate validation settings, random sources, and plaintext channels across clients and services.
- Determine which secrets, identities, signatures, or data protections depend on the affected primitive or validation path.
- Check debug, compatibility, fallback, and hostname or audience override settings in build and runtime configuration.
Remediate safely
- Use a maintained platform cryptographic API with approved algorithms, modes, parameters, randomness, and full peer identity validation.
- Remove insecure fallback and validation bypasses; separate keys by purpose and load them from managed secret storage.
- Plan rotation or reissuance for affected keys, certificates, tokens, hashes, or ciphertext and document compatibility sequencing.
Authoritative sources
Complete CVE record and remediation plan
The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.