HighGHSA-ff7q-6vwh-v9m4CVE-2023-52892
Name confusion in x509 Subject Alternative Name fields
Published 28 Jun 2024 · Updated 28 Jun 2024
Affected packages
phpseclib/phpseclibComposer
- Affected
- <1.0.22
- Fixed in
- 1.0.22
Update to the fixed version for your release line, for example:
composer require phpseclib/phpseclib:^1.0.22phpseclib/phpseclibComposer
- Affected
- >=2.0.0 <2.0.46
- Fixed in
- 2.0.46
Update to the fixed version for your release line, for example:
composer require phpseclib/phpseclib:^2.0.46phpseclib/phpseclibComposer
- Affected
- >=3.0.0 <3.0.33
- Fixed in
- 3.0.33
Update to the fixed version for your release line, for example:
composer require phpseclib/phpseclib:^3.0.33Details
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.
Is GHSA-ff7q-6vwh-v9m4 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected phpseclib/phpseclib, and gives you the command that fixes it.
References
- Advisorynvd.nist.gov/vuln/detail/CVE-2023-52892
- Linkgithub.com/phpseclib/phpseclib/issues/1943
- Linkgithub.com/phpseclib/phpseclib/commit/6cd6e8ceab9f2b55c8cd81d2192bf98cbeaf4627
- Packagegithub.com/phpseclib/phpseclib
- Linkgithub.com/phpseclib/phpseclib/releases/tag/3.0.33
- Linkgithub.com/x509-name-testing/name_testing_artifacts
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.