Quick answers
- Is CVE-2023-31317 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2023-31317 being exploited in the wild.
- How severe is CVE-2023-31317?
- Informational severity, with a CVSS score of 8.8, published 15 May 2026.
- Which products and versions are affected?
- AMD Secure Processor (ASP).
- Is there a fix for CVE-2023-31317?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2023-31317 attacked?
- It is attacked with local access, in device firmware.
- Am I affected by CVE-2023-31317?
- Check whether you run Amd Secure Processor. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
This vulnerability is classified as a memory buffer overflow (CWE-119) within the AMD Secure Processor (ASP) firmware. The flaw stems from improper restriction of operations within the bounds of a memory buffer. An attacker with local access and low privileges could exploit this to perform unauthorized read or write operations on protected memory regions. Successful exploitation could lead to arbitrary code execution within the context of the ASP, effectively compromising the hardware-based Root of Trust. The attack requires high complexity (AC:H) but can result in a total loss of confidentiality, integrity, and availability across both the local and virtualized environments.
Affected products
- AMD Secure Processor (ASP)
Timeline
- 2026-05-15: disclosed: NVD publication date