CVE-2023-32690
libspdm is a sample implementation that follows the DMTF SPDM specifications.
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (0.71%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
Description
libspdm is a sample implementation that follows the DMTF SPDM specifications. Prior to versions 2.3.3 and 3.0, following a successful CAPABILITIES response, a libspdm Requester stores the Responder's CTExponent into its context without validation. If the Requester sends a request message that requires a cryptography operation by the Responder, such as CHALLENGE, libspdm will calculate the timeout value using the Responder's unvalidated CTExponent. A patch is available in version 2.3.3. A workaround is also available. After completion of VCA, the Requester can check the value of the Responder's CTExponent. If it greater than or equal to 64, then the Requester can stop communication with the Responder.
- CVSS 3.1
- 7.5 HIGHCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- EPSS
- 0.71% probability · 52th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-20
- Affected
- dmtf/libspdm
- Source
- security-advisories@github.com
References
- https://github.com/DMTF/libspdm/issues/2068Patch
- https://github.com/DMTF/libspdm/pull/2069Patch
- https://github.com/DMTF/libspdm/security/advisories/GHSA-56h8-4gv5-jf2cVendor Advisory
- https://github.com/DMTF/libspdm/issues/2068Patch
- https://github.com/DMTF/libspdm/pull/2069Patch
- https://github.com/DMTF/libspdm/security/advisories/GHSA-56h8-4gv5-jf2cVendor Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.