CVE-2023-31313
Raw vector
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-31313 is a high-severity Confused Deputy (CWE-441) vulnerability in Amd (inferred from references). Its CVSS base score is 7.2 (High).
Operationally, ranked at the 1th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-16 (Security and Privacy Attributes) and AC-4 (Information Flow Enforcement) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2023-31313 is a vulnerability in the AMD power management firmware (PMFW) involving an unintended proxy or intermediary that could allow a privileged attacker to send malformed messages to the system management unit (SMU), potentially resulting in arbitrary code execution. Published on 2026-02-12, it carries a CVSS v3.1 base score of 7.2 (AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:N) and maps to CWE-441 (Unintended Proxy or Intermediary ('Confused Deputy')).
The attack requires local access with high privileges (PR:H) and high attack complexity (AC:H), but no user interaction. A successful exploit enables the attacker to achieve arbitrary code execution with high impacts on confidentiality and integrity, no impact on availability, and a changed scope due to the firmware context.
AMD's security bulletin provides details on mitigation; practitioners should refer to https://www.amd.com/en/resources/product-security/bulletin/AMD-SB-6024.html for patch information and remediation guidance.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-35624
Vulnerability Data
An unintended proxy or intermediary in the AMD power management firmware (PMFW) could allow a privileged attacker to send malformed messages to the system management unit (SMU) potentially resulting in arbitrary code execution.
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Associating and preserving security attributes such as original source identity prevents the loss of provenance that creates the confused deputy.
Information flow enforcement requires preserving and checking source attributes before forwarding requests outside the trust boundary.
Access enforcement directly stops a component from acting on forwarded requests without verifying original source authorizations.
Boundary protection limits and inspects external forwarding, reducing the ability of an intermediary to act as an unintended proxy.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
A.5.15 only requires defining and documenting an access control policy plus requirements; it does not itself enforce rules or stop a confused-deputy proxy from being introduced or exploited.
A.5.16 governs identity lifecycle, uniqueness, accountability and timely removal to support proper access rights assignment; it has no bearing on preserving original request sources or stopping confused-deputy proxying when a product forwards an upstream request.
Explicit access-rights assignment can restrict the product’s ability to act as an unintended proxy for external actors.
Privileged-access controls limit the rights the product may exercise on behalf of upstream callers, mitigating confused-deputy abuse.
Network-security controls can enforce source validation and prevent the product from blindly proxying traffic to external actors.
Secure-SDLC practices include design reviews that detect and eliminate confused-deputy proxy patterns before deployment.
Hardening callouts derived
DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.
- No fine-grained STIG row for CWE-441, a class-level weakness, and none of its children carries one either.