CVE-2023-31317
Memory bounds violation in AMD ASP could enable local RCE.
Is CVE-2023-31317 being exploited?
Not confirmed. CVE-2023-31317 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.10% probability of exploitation in the next 30 days.
How severe is CVE-2023-31317?
CVE-2023-31317 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2023-31317?
Not known from our data. No patch reference has been recorded for CVE-2023-31317, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2023-31317 affect?
CVE-2023-31317 affects AMD Secure Processor (ASP). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2023-31317?
Monitor advisories; apply ASP firmware/BIOS updates when released.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Local attacker could read/write protected ASP memory and achieve arbitrary code execution.
Monitor only