CVE-2023-31127
What it is
libspdm is a sample implementation that follows the DMTF SPDM specifications. A vulnerability has been identified in SPDM session establishment in libspdm prior to version 2.3.1. If a device supports both DHE session and PSK session with mutual authentication, the attacker may be able to establish the session with `KEY_EXCHANGE` and `PSK_FINISH` to bypass the mutual authentication. This is most likely to happen when the Requester begins a session using one method (DHE, for example) and then uses the other method's finish (PSK_FINISH in this example) to establish the session. The session hashes would be expected to fail in this case, but the condition was not detected. This issue only impacts the SPDM responder, which supports `KEY_EX_CAP=1 and `PSK_CAP=10b` at same time with mutual authentication requirement. The SPDM requester is not impacted. The SPDM responder is not impacted if `KEY_EX_CAP=0` or `PSK_CAP=0` or `PSK_CAP=01b`. The SPDM responder is not impacted if mutual authentication is not required. libspdm 1.0, 2.0, 2.1, 2.2, 2.3 are all impacted. Older branches are not maintained, but users of the 2.3 branch may receive a patch in version 2.3.2. The SPDM specification (DSP0274) does not contain this vulnerability.
At a glance
- Exploitability
- Can be exploited from the same network segment with a low-privilege account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.9% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.9% in the next 30 days (EPSS).
- Severity: 9.0 CRITICAL (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.9% · EPSS, next 30 days
- Weakness
- CWE-287 · Improper authentication
- Record status
- Modified
Affected
- Dmtf Libspdm < 2.3.2
Attack profile CVSS 3.1 · 9.0
- Attack vector
- Adjacent network
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2023-31127.md and follow it. Check whether this project is affected by CVE-2023-31127. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://github.com/DMTF/libspdm/pull/2006
- https://github.com/DMTF/libspdm/pull/2007
- https://github.com/DMTF/libspdm/security/advisories/GHSA-qw76-4v8p-xq9f
- https://github.com/DMTF/libspdm/pull/2006
- https://github.com/DMTF/libspdm/pull/2007
- https://github.com/DMTF/libspdm/security/advisories/GHSA-qw76-4v8p-xq9f
References
- https://github.com/DMTF/libspdm/pull/2006
- https://github.com/DMTF/libspdm/pull/2007
- https://github.com/DMTF/libspdm/security/advisories/GHSA-qw76-4v8p-xq9f
- https://github.com/DMTF/libspdm/pull/2006
- https://github.com/DMTF/libspdm/pull/2007
- https://github.com/DMTF/libspdm/security/advisories/GHSA-qw76-4v8p-xq9f