Name confusion in x509 Subject Alternative Name fields
In phpseclib before 1.0.22, 2.x before 2.0.46, and 3.x before 3.0.33, some characters in Subject Alternative Name fields in TLS certificates are incorrectly allowed to have a special meaning in regular expressions (such as a + wildcard), leading to name confusion in X.509 certificate host verification.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2023-52892US | — | — | ||
In phpseclib before 1.0.22, 2.x before 2.0.46, and 3.x before 3.0.33, some characters in Subject Alternative Name fields in TLS certificates are incorrectly allowed to have a speci… | ||||
02
references
External citations — patches, advisories, analysis.
- https://github.com/phpseclib/phpseclibPACKAGE
- https://github.com/phpseclib/phpseclib/commit/6cd6e8ceab9f2b55c8cd81d2192bf98cbeaf4627WEB
- https://github.com/phpseclib/phpseclib/issues/1943WEB
- https://github.com/phpseclib/phpseclib/releases/tag/3.0.33WEB
- https://github.com/x509-name-testing/name_testing_artifactsWEB
- https://nvd.nist.gov/vuln/detail/CVE-2023-52892ADVISORY
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan