Skip to main content
VulnerabilityPublished

Crypton x509 validation: Improper IP address validation in validateCertificateName

Affects crypton-x509-validationSource GCVE Database

0
Severity
High

Rated High by Threat Radar's AI analysis

Patch
Available – fixed in 1.10.2

Data as of 17 Nov 2026, 11:03 UTC

What to do

Upgrade crypton-x509-validation to 1.10.2.

Affected software

ProductAffectedFixed in
Hackagecrypton-x509-validationAffected
  • >=1.6.12 <1.10.2
Fixed in
  • 1.10.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade crypton-x509-validation to version 1.10.2 or later, where the issue is fixed. The fix ensures proper validation of iPAddress SAN entries and enforces the documented behavior that SAN extensions supersede commonName.

Description

crypton-x509-validation versions from 1.6.12 up to but not including 1.10.2 improperly validate IP addresses in certificates by ignoring the iPAddress subjectAltName (SAN) when no dNSName SAN is present. This causes clients to accept certificates with a commonName (CN) matching the target IP but an iPAddress SAN pointing elsewhere, violating expected SAN precedence rules. The flaw allows impersonation if a trusted CA issues such a certificate, typically possible only with private or enterprise CAs. The issue is fixed in version 1.10.2.

References

Community reviews

Loading reviews…