First published: Thu Jun 01 2023(Updated: )
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.
Credit: security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
DMTF Libspdm | <2.3.3 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2023-32690 is a vulnerability in the libspdm software prior to versions 2.3.3 and 3.0, which allows a malicious Responder to store CTExponent into the Requester's context without validation.
The severity of CVE-2023-32690 is high, with a severity value of 7.5.
CVE-2023-32690 affects libspdm versions prior to 2.3.3 and 3.0 by allowing a malicious Responder to store CTExponent into the Requester's context without validation.
To fix CVE-2023-32690, you should update to a version of libspdm that is equal to or later than 2.3.3.
The Common Weakness Enumeration (CWE) ID for CVE-2023-32690 is 20.