Описание
cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. Prior to 49.0.0, if an intermediate constrained CA permits the DNS name foo.example.com, and the leaf certificate has a wildcard in its DNS SAN of *.example.com, python-cryptography's verifier accepts which allows escaping outside of the permitted names. The core issue is in DNSConstraint::matches, where a wildcard pattern was treated as matching a more-specific permitted constraint even though *.example.com can expand to sibling names such as bar.example.com outside foo.example.com. This allows acceptance of an invalid certificate chain. This issue is fixed in 49.0.0.
A flaw was found in python-cryptography versions 46.0.6 through 48.x. The X.509 verifier incorrectly handles wildcard DNS Subject Alternative Names when evaluating permitted name constraints: a leaf SAN such as *.example.com may be accepted under a more specific permitted subtree (for example foo.example.com), allowing escape to sibling names outside the permitted set. This can lead to acceptance of an invalid certificate chain. Ordinary Web PKI topologies are not affected.
Отчет
Red Hat scores High confidentiality and integrity because a successful bypass accepts an invalid certificate chain (name-constraint escape), while Attack Complexity is High because exploitation requires a DNS-constrained intermediate CA that issues a broader wildcard leaf SAN than its permitted subtree—topology that Web PKI does not use. Vulnerable code was introduced in cryptography 46.0.6 (DNSConstraint::matches / PR #14542) and fixed in 49.0.0; versions before 46.0.6 are not affected by this specific permittedSubtrees escape.
Меры по смягчению последствий
Red Hat is not aware of a practical temporary workaround that fully mitigates this issue or meets Red Hat Product Security's standards for usability, deployment, applicability, or stability. Customers are advised to apply the relevant security updates when/if they become available.
Затронутые пакеты
| Платформа | Пакет | Состояние | Рекомендация | Релиз |
|---|---|---|---|---|
| Red Hat Ansible Automation Platform 2 | python3.11-cryptography | Not affected | ||
| Red Hat Ansible Automation Platform 2 | python3.12-cryptography | Fix deferred | ||
| Red Hat Ansible Automation Platform 2 | python3x-cryptography | Not affected | ||
| Red Hat Ansible Automation Platform 2 | python-cryptography | Fix deferred | ||
| Red Hat Enterprise Linux 10 | python-cryptography | Not affected | ||
| Red Hat Enterprise Linux 7 | python-cryptography | Not affected | ||
| Red Hat Enterprise Linux 8 | python3.12-cryptography | Not affected | ||
| Red Hat Enterprise Linux 8 | python-cryptography | Not affected | ||
| Red Hat Enterprise Linux 9 | python3.12-cryptography | Not affected | ||
| Red Hat Enterprise Linux 9 | python-cryptography | Not affected |
Показывать по
Ссылки на источники
Дополнительная информация
Статус:
EPSS
7.4 High
CVSS3
Связанные уязвимости
cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. In versions 45.0.0 through 48.0.0, if an intermediate constrained CA permits the DNS name foo.example.com, and the leaf certificate has a wildcard in its DNS SAN of *.example.com, python-cryptography's verifier accepts which allows escaping outside of the permitted names. The core issue is in DNSConstraint::matches, where a wildcard pattern was treated as matching a more-specific permitted constraint even though *.example.com can expand to sibling names such as bar.example.com outside foo.example.com. This allows acceptance of an invalid certificate chain. This issue is fixed in 49.0.0.
cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. In versions 45.0.0 through 48.0.0, if an intermediate constrained CA permits the DNS name foo.example.com, and the leaf certificate has a wildcard in its DNS SAN of *.example.com, python-cryptography's verifier accepts which allows escaping outside of the permitted names. The core issue is in DNSConstraint::matches, where a wildcard pattern was treated as matching a more-specific permitted constraint even though *.example.com can expand to sibling names such as bar.example.com outside foo.example.com. This allows acceptance of an invalid certificate chain. This issue is fixed in 49.0.0.
python-cryptography verifier accepts wildcard DNS names allowing escape from permittedSubtrees
cryptography is a package designed to expose cryptographic primitives ...
python-cryptography verifier accepts wildcard DNS names allowing escape from permittedSubtrees
EPSS
7.4 High
CVSS3