Export
The link always opens the latest version of this page.
Ask an AI about it
Open in ChatGPTA new chat that reads this entry from the site Open in ClaudeThe same, in ClaudeShare the link instead of a file, and they will always see the latest version.
Files are a snapshot of today. The live page has anything newer.
VU#573195
Name Constraint inconsistency across TLS libraries (Go, OpenSSL, Apple, LibreSSL, pyca, wolfSSL) due to differing DNS case sensitivity, IPv4-mapped IPv6 handling, URI parsing, and wildcard matching interpretations
- Weakness
- Name Constraints 1 source
Definition: VU#573195 is a vulnerability affecting multiple TLS certificate validation libraries stemming from inconsistent implementation of X.509 Name Constraints across different platforms and cryptographic libraries.
Affected Products
The vulnerability impacts six major TLS libraries 1:
- Go crypto/x509
- OpenSSL
- Apple Security.framework
- LibreSSL
- pyca/cryptography
- WolfSSL
Technical Issue
The core weakness involves name-constraints validation, where different libraries interpret and enforce certificate name constraints inconsistently 1. This inconsistency arises from divergent handling of several DNS and IP address parsing scenarios:
- DNS case sensitivity: Libraries differ in whether they normalize domain names to lowercase before constraint matching
- IPv4-mapped IPv6 addresses: Inconsistent treatment of IPv4 addresses represented in IPv6 format (e.g.,
::ffff:192.0.2.1) - URI parsing: Variations in how URIs are parsed when validating against name constraints
- Wildcard matching: Different interpretations of wildcard certificate matching rules within constrained namespaces
Security Impact
These inconsistencies can allow a certificate issued under name constraints to be accepted by some libraries while rejected by others. An attacker holding a constrained certificate could potentially bypass intended restrictions on one platform while the same certificate would be properly rejected on another, creating a fragmented security posture across different systems and applications.
Mitigation
Organizations should monitor updates from affected library maintainers and apply patches as they become available. The vulnerability highlights the importance of standardized X.509 validation behavior across cryptographic implementations.
Facts 1
| Attribute | Value | Confidence | Sources | Cited |
|---|---|---|---|---|
| Weakness | Name Constraints | low | 1 | 1 |
Affected product 6
Sources 1
- VU#573195: Go, OpenSSL, Apple, LibreSSL, pyca, wolfSSL Name-Constraint inconsistency in RFC 5280 implementation · CERT/CC Vulnerability Notes