dbcve.org
Memory Buffer Bounds ErrorWeakness · CWE-119

CVE-2023-31317

HIGH · 8.8 CVSS v4.0 Published 2026-05-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper restriction of operations within the bounds of a memory buffer in the AMD secure processer (ASP) could allow an attacker to read or write to protected memory potentially resulting in arbitrary code execution.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A memory buffer bounds restriction vulnerability in the AMD Secure Processor (ASP) firmware allows an attacker to read or write to protected memory regions, potentially achieving arbitrary code execution within the trusted execution environment.

MitigationApply AMD-provided firmware updates for the Secure Processor; verify the patch status through AMD's firmware verification tools and ensure systems are running the latest silicon-specific security microcode.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
High
Privileges
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify AMD Secure Processor presence
    Check if the system has AMD Secure Processor hardware. On Windows, run 'msinfo32' and look for 'AMD Secure Processor' in the components list. On Linux, run 'lspci | grep -i amd' or check /sys/devices/system/cpu/cpu0/topology/ to identify AMD platform.
    Affected if The system does not show an AMD Secure Processor listed in hardware information
  2. Check ASP firmware version on Windows
    Open Device Manager, expand 'System devices', right-click 'AMD Secure Processor', select Properties, go to the Firmware tab, and note the firmware version number displayed.
    Affected if The displayed firmware version is lower than AMD's latest published version for this component
  3. Check ASP firmware version on Linux
    Run 'cat /sys/class/misc/amd_spi/version' or use 'dmidecode -t processor' to extract Secure Processor firmware information. Some systems expose this via 'cat /sys/firmware/efi/fw_platform_size' combined with platform-specific tools.
    Affected if The firmware version cannot be determined or is older than AMD's published patch versions
  4. Verify security microcode status
    Check if the system has applied the latest platform-specific security updates. On Linux, run 'dmesg | grep -i microcode' to see loaded microcode version. On Windows, check Windows Update for AMD platform updates.
    Affected if The microcode version loaded at boot is outdated or no recent security updates have been applied to the platform firmware
  5. Confirm ASP is enabled in firmware settings
    Enter system BIOS/UEFI setup (typically press Delete or F2 at boot), navigate to Security or Advanced settings, and verify 'AMD Secure Processor' or 'PSP' (Platform Security Processor) is set to Enabled.
    Affected if The AMD Secure Processor is disabled in UEFI/BIOS settings, or access to firmware version information is restricted

A system is affected if it has an AMD Secure Processor with firmware version lower than AMD's latest published version for this CVE, and the ASP is enabled in the hardware/firmware configuration.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply AMD-provided firmware updates for the Secure Processor; verify the patch status through AMD's firmware verification tools and ensure systems are running the latest silicon-specific security microcode.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-31317 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-31317 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data