CVE-2023-32690: libspdm is a sample implementation that follows the DMTF SPDM specifications

Q: How do I fix CVE-2023-32690?

libspdm: upgrade to 2.3.3. Exact commands for each OS are on this page.

Q: Is CVE-2023-32690 being exploited?

CVE-2023-32690 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2023-32690 affect?

CVE-2023-32690 affects libspdm. Severity is medium (CVSS 5.7). 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 vali

Q: How urgent is CVE-2023-32690?

Priority 33/100. No elevated risk signals yet.

Routine

MEDIUM 5.7UPGRADE

CVE-2023-32690 is a medium-severity flaw (CVSS 5.7) affecting libspdm. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	5.7 (Medium)
Attack vector	Adjacent network
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.7% (top 46%)
CISA exploited list	No
Weakness	CWE-20
Published	2023-06-01
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: dmtf

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2023-06-01 17:15 UTCPublished CVE record published
2026-06-17 05:59 UTCUpdated Record last modified

dmtf libspdm UPGRADE

Affected: < 2.3.3

Fixed in: 2.3.3

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy libspdm || rpm -q libspdm || libspdm --version

2. UPGRADE to 2.3.3 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade libspdm

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade libspdm

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2023-32690?

libspdm: upgrade to 2.3.3. Exact commands for each OS are on this page.

Is CVE-2023-32690 being exploited?

CVE-2023-32690 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2023-32690 affect?

CVE-2023-32690 affects libspdm. Severity is medium (CVSS 5.7). 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 vali

How urgent is CVE-2023-32690?

Priority 33/100. No elevated risk signals yet.

Related CVEs

CVE-2023-31127 CRITICAL 9.0 UPGRADE libspdm is a sample implementation that follows the DMTF SPDM specifications

References

← Back to latest CVEs