Improper IP address validation in validateCertificateName
Data.X509.Validation.getNames extracts only
AltNameDNS entries from the subjectAltName extension
(Data/X509/Validation.hs, unAltName, ~L512–515 in
crypton-x509-validation 1.10.1). When a certificate carries an
iPAddress SAN but no dNSName SAN, the
extracted name list is empty, so validateNames (~L569–580)
falls through to the commonName branch as if no SAN extension existed,
even though the extension's haddock promises that the commonName is
ignored whenever subjectAltName is present. Consequently, when a client
connects to an IP literal:
- a certificate with
CN = <target IP>butiPAddressSAN pointing to a different host is accepted; - a certificate whose only valid identity is a matching
iPAddressSAN is rejected.
Exploitation requires a certificate from a CA the client trusts that has a commonName different from its iPAddress SAN (public CAs are barred from this by the CA/Browser Forum Baseline Requirements, but private or enterprise CAs can issue such certificates). A successful impersonation exposes and can modify the protected connection.
The draft fix makes getNames distinguish "no SAN
extension" from "SAN extension present with no DNS names" and applies
SAN semantics (including the existing iPAddress comparison) whenever the
extension is present, restoring the documented SAN-supersedes-CN
behavior in line with RFC 9525. No fixed release is published at the
time of writing (1.10.1 is the latest release and still vulnerable).
Credits
Reported by Dickson Wu (SEAL & CertiK). Validated and fixed by Kazu Yamamoto.
Info
- Published
- November 17, 2026
- Modified
- November 17, 2026
- CAPECs
- < none >
- CWEs
- 297
- Keywords
- tls, x509, hostname-validation, ip-address, cn-fallback
- Aliases
- < none >
- Related
- < none >
- References
- [PACKAGE] https://hackage.haskell.org/package/crypton-x509-validation
- [FIX] https://github.com/kazu-yamamoto/crypton-certificate/commit/d2f64137954b4026332fa9f08c1711bd92c79d62
- [FIX] https://github.com/kazu-yamamoto/crypton-certificate/commit/d782c2dd83e69d2ed103ed42fdac95d94262e7d3
Affected
@hackage/crypton-x509-validation
- CVSS
- CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
- Versions
>=1.6.12 && <1.10.2- Declarations
- < none >
- Affected APIs
Data.X509.Validation.validateCertificateNameData.X509.Validation.validateDefault