Technical impact
libspdm_x509_verify_cert_chain() validates certificate signatures incrementally instead of verifying the entire X.509 path, meaning the CA nameConstraints and pathLenConstraint are not enforced. This flaw allows an attacker who possesses a subordinate issuer certificate that exceeds the CA constraints to present a certificate that is accepted as a valid SPDM identity, effectively enabling identity impersonation. The weakness is classified under CWE-295: Improper Certificate Validation, and can impact the confidentiality and integrity of SPDM authentication in systems relying on libspdm for identity verification.
Affected Systems
DMTF:libspdm is affected, with the issue present in all releases prior to 3.8.3 and prior to 4.0.0‑rc2. Applications using libspdm versions 3.8.2 or earlier, or 4.0.0‑rc1 or earlier, are vulnerable until the corresponding security fix is applied.
Risk and Exploitability
The CVSS score of 4.4 indicates a low‑to‑medium severity, and no EPSS score is available, suggesting a low probability of active exploitation. The vulnerability is not listed in the CISA KEV catalog. Exploitation requires a deployment that uses libspdm’s backend validation without supplementary chain validation mechanisms, relies on a pinned root that cannot be substituted, and has a measurement policy that permits identity impersonation alone to satisfy acceptance. In such constrained scenarios, an attacker could bypass pathLenConstraint or nameConstraints restrictions by presenting a subordinate certificate, but broad applicability is limited because many deployments include additional validation or policy checks. The mbedTLS backend also lacks nameConstraints enforcement, which further constrains the real‑world risk.