HSEC-2023-0006 json
x509-validation does not enforce pathLenConstraint
published 2025-11-14 11 mo ago modified 2025-11-14 11 mo ago
- cvss
- 5.7
- version 3.1, OSV
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
# x509-validation does not enforce pathLenConstraint
*x509-validation* prior to version 1.4.8 did not enforce the pathLenConstraint value. Constrained CAs could accidentally (or deliberately) issue CAs below the maximum depth and *x509-validation* would accept certificates issued by the unauthorised intermediate CAs.
Patch / fix
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| OSV | 3.1 | 5.7 | CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| hackage | x509-validation | >=1.4.0, <1.4.8 |
1.4.8 |
References
Sources
- OSV HSEC-2023-0006
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.