CyberSecBulletin
CVE-2022-23829NVD status: Deferred

AMD Ryzen™ Threadripper™ PRO Processors 5900…: Improper Access Control

CVE-2022-23829 is a high-severity improper access control vulnerability in AMD Ryzen™ Threadripper™ PRO Processors 5900 WX-Series from AMD, with a CVSS 3.1 base score of 8.2 out of 10. It can be exploited with local access to the system by an attacker with administrator privileges, without any action from a user. Affected AMD Ryzen™ Threadripper™ PRO Processors 5900 WX-Series versions: various. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.2% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Check which version of AMD Ryzen™ Threadripper™ PRO Processors 5900 WX-Series you run against the affected versions below, and install the vendor's latest release.

Affected products and versions

VendorProductAffected versionsFixed in
AMDAMD Ryzen™ Threadripper™ PRO Processors 5900 WX-SeriesvariousNot stated
AMDAMD Ryzen™ 6000 Series Mobile Processors and WorkstationsvariousNot stated
AMDAMD Ryzen™ 7000 Series Desktop ProcessorsvariousNot stated
AMDAMD Ryzen™ 5000 Series Mobile ProcessorsvariousNot stated
AMDAMD Ryzen™ 5000 Series Desktop ProcessorsvariousNot stated
AMDAMD Ryzen™ 5000 Series Mobile Processors with Radeon™ GraphicsvariousNot stated
AMDAMD Ryzen™ 3000 Series Desktop ProcessorsvariousNot stated
AMDAMD Ryzen™ 4000 Series Desktop Processors with Radeon™ GraphicsvariousNot stated
AMDAMD Ryzen™ 4000 Series Mobile ProcessorsvariousNot stated
AMDAMD Ryzen™ 3000 Series Mobile Processor / 2nd Gen AMD Ryzen™ Mobile Processor with Radeon™ GraphicsvariousNot stated
AMDAMD Athlon™ 3000 Series Mobile Processors with Radeon™ GraphicsvariousNot stated
AMDAMD Ryzen™ Threadripper™ PRO ProcessorvariousNot stated
AMD1st Gen AMD EPYC™ ProcessorsvariousNot stated
AMD2nd Gen AMD EPYC™ ProcessorsvariousNot stated
AMD3rd Gen AMD EPYC™ ProcessorsvariousNot stated
AMDAMD EPYC™ Embedded 3000variousNot stated
AMDAMD EPYC (TM) Embedded 7002variousNot stated
AMDAMD EPYC™ Embedded 7003variousNot stated
AMDAMD RyzenTM Embedded R1000variousNot stated
AMDAMD RyzenTM Embedded R2000variousNot stated
AMDAMD RyzenTM Embedded 5000variousNot stated
AMDAMD RyzenTM Embedded V1000variousNot stated
AMDAMD RyzenTM Embedded V2000variousNot stated
AMDAMD RyzenTM Embedded V3000variousNot stated
AMDryzen_threadripper_pro_5995wxall versionsNot stated

Version data comes from the organisation that assigned the CVE; 1 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
HighAdministrator-level access is required first.
User interaction
NoneNo action by a victim is required.
Scope
ChangedThe attack can reach beyond the vulnerable component into other systems.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H. Scored by CNA (amd.com).

Official description

A potential weakness in AMD SPI protection features may allow a malicious attacker with Ring0 (kernel mode) access to bypass the native System Management Mode (SMM) ROM protections.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Improper Access Control

The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

How developers prevent this class of flaw

  • Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
  • Compartmentalize the system to have safe areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

More Improper Access Control vulnerabilities (CWE-284)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Improper Access Control vulnerabilities

Spotted an error? Tell us.