cryptography has incomplete DNS name constraint enforcement on peer names
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 46.0.6.
cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. Prior to version 46.0.6, DNS name constraints were only validated against SANs within child certificates, and not the "peer name" presented during each validation. Consequently, cryptography would allow a peer named bar.example.com to validate against a wildcard leaf certificate for *.example.com, even if the leaf's parent certificate (or upwards) contained an excluded subtree constraint for bar.example.com. This issue has been patched in version 46.0.6.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| cryptography.io | cryptography | >=45.0.0 <46.0.6 | 46.0.6 |
| pyca | <46.0.6 |
Coverage
News and research mentioning this CVE
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket