{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-32690 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-32690 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-32690 is a medium-severity vulnerability in DMTF libspdm, published on 1 Jun 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2023-32690 and fix it if it is affected.\n\nWhat it is: CVE-2023-32690 is a medium-severity vulnerability in DMTF libspdm, published on 1 Jun 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2023-32690 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-32690/ (Markdown: https://insights.sbomify.com/CVE-2023-32690/index.md)","id":"CVE-2023-32690","markdown":"https://insights.sbomify.com/CVE-2023-32690/index.md","name":"CVE-2023-32690","record":{"aliases":["GHSA-56h8-4gv5-jf2c"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"SPDM security library","requires_auth":"none","summary":"An attacker can cause undefined behavior and potential denial of service in libspdm Requesters by providing an unvalidated CTExponent value.","user_interaction":"required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"libspdm","vendor":"dmtf"}],"cvss":{"score":5.7,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"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.\n\nA 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.","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":"Responder can Invoke Undefined Behavior in libspdm Requester","id":"CVE-2023-32690","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2023"},"n_packages":0,"n_references":3,"next":{"headline":"ginuerzh/gost vulnerable to Timing Attack","id":"CVE-2023-32691"},"packages":[],"prev":{"headline":"Parse Server vulnerable to phishing attack vulnerability that involves uploading malicious HTML file","id":"CVE-2023-32689"},"products":["libspdm"],"published":"2023-06-01","related":[{"cvss_score":9.1,"headline":"DMTF-2023-0001: SPDM mutual authentication bypass","id":"CVE-2023-31127","kev_date_added":null,"published":"2023-05-08"}],"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":"partial"},"state":"PUBLISHED","updated":"2025-01-08","vendors":["DMTF"]},"summary":"An attacker can cause undefined behavior and potential denial of service in libspdm Requesters by providing an unvalidated CTExponent value.","url":"https://insights.sbomify.com/CVE-2023-32690/"}