{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-31127 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-31127 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-31127 is a critical authentication bypass vulnerability in DMTF libspdm, published on 8 May 2023. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-31127 and fix it if it is affected.\n\nWhat it is: CVE-2023-31127 is a critical authentication bypass vulnerability in DMTF libspdm, published on 8 May 2023. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-31127 in the wild and no public exploit code.\n\nAffected product: DMTF libspdm. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-31127/ (Markdown: https://insights.sbomify.com/CVE-2023-31127/index.md)","id":"CVE-2023-31127","markdown":"https://insights.sbomify.com/CVE-2023-31127/index.md","name":"CVE-2023-31127","record":{"aliases":["GHSA-qw76-4v8p-xq9f"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"SPDM security library","requires_auth":"low_privilege","summary":"Attackers can bypass mutual authentication in SPDM session establishment by mixing DHE and PSK methods, affecting libspdm responders with specific capabilities.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"libspdm","vendor":"dmtf"}],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-372","name":"Incomplete Internal State Distinction"},{"id":"CWE-287","name":"Improper Authentication"}],"description":"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\nauthentication, 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.\n\nThis 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.\n\nlibspdm 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"DMTF-2023-0001: SPDM mutual authentication bypass","id":"CVE-2023-31127","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2023"},"n_packages":0,"n_references":3,"next":{"headline":"NextCloud Cookbook's pull-checks.yml workflow is vulnerable to OS Command Injection","id":"CVE-2023-31128"},"packages":[],"prev":{"headline":"Improper Neutralization of Invalid Characters in Data Attribute Names in org.xwiki.commons:xwiki-commons-xml","id":"CVE-2023-31126"},"products":["libspdm"],"published":"2023-05-08","related":[{"cvss_score":5.7,"headline":"Responder can Invoke Undefined Behavior in libspdm Requester","id":"CVE-2023-32690","kev_date_added":null,"published":"2023-06-01"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-01-28","vendors":["DMTF"]},"summary":"Attackers can bypass mutual authentication in SPDM session establishment by mixing DHE and PSK methods, affecting libspdm responders with specific capabilities.","url":"https://insights.sbomify.com/CVE-2023-31127/"}