AMD RyzenTM Embedded V3000 AMD SPI Protection access control

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.4$0-$5k0.00

Summaryinfo

A vulnerability identified as critical has been detected in AMD Ryzen Threadripper PRO Processors 5900 WX-Series, Ryzen 6000 Series Mobile Processors and Workstations, Ryzen 7000 Series Desktop Processors, Ryzen 5000 Series Mobile Processors, Ryzen 5000 Series Desktop Processors, Ryzen 5000 Series Mobile Processors with Radeon Graphics, Ryzen 3000 Series Desktop Processors, Ryzen 4000 Series Desktop Processors with Radeon Graphics, Ryzen 4000 Series Mobile Processors, Ryzen 3000 Series Mobile Processor , 2nd Gen Ryzen Mobile Processor with Radeon Graphics, Athlon 3000 Series Mobile Processors with Radeon Graphics, Ryzen Threadripper PRO Processor, 1st Gen EPYC Processors, 2nd Gen EPYC Processors, 3rd Gen EPYC Processors, EPYC Embedded 3000, EPYC (TM) Embedded 7002, EPYC Embedded 7003, RyzenTM Embedded R1000, RyzenTM Embedded R2000, RyzenTM Embedded 5000, RyzenTM Embedded V1000, RyzenTM Embedded V2000 and RyzenTM Embedded V3000. Affected by this issue is some unknown functionality of the component AMD SPI Protection. The manipulation leads to Local Privilege Escalation. This vulnerability is uniquely identified as CVE-2022-23829. Local access is required to approach this attack. No exploit exists.

Detailsinfo

A vulnerability was found in AMD Ryzen Threadripper PRO Processors 5900 WX-Series, Ryzen 6000 Series Mobile Processors and Workstations, Ryzen 7000 Series Desktop Processors, Ryzen 5000 Series Mobile Processors, Ryzen 5000 Series Desktop Processors, Ryzen 5000 Series Mobile Processors with Radeon Graphics, Ryzen 3000 Series Desktop Processors, Ryzen 4000 Series Desktop Processors with Radeon Graphics, Ryzen 4000 Series Mobile Processors, Ryzen 3000 Series Mobile Processor , 2nd Gen Ryzen Mobile Processor with Radeon Graphics, Athlon 3000 Series Mobile Processors with Radeon Graphics, Ryzen Threadripper PRO Processor, 1st Gen EPYC Processors, 2nd Gen EPYC Processors, 3rd Gen EPYC Processors, EPYC Embedded 3000, EPYC (TM) Embedded 7002, EPYC Embedded 7003, RyzenTM Embedded R1000, RyzenTM Embedded R2000, RyzenTM Embedded 5000, RyzenTM Embedded V1000, RyzenTM Embedded V2000 and RyzenTM Embedded V3000 and classified as critical. This issue affects some unknown functionality of the component AMD SPI Protection. The manipulation with an unknown input leads to a local privilege escalation vulnerability. Using CWE to declare the problem leads to CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

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.

It is possible to read the advisory at amd.com. The identification of this vulnerability is CVE-2022-23829 since 01/21/2022. The exploitation is known to be easy. Attacking locally is a requirement. Additional levels of successful authentication are required for exploitation. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 06/19/2024). The attack technique deployed by this issue is T1068 according to MITRE ATT&CK.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

Name

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.4
VulDB Meta Temp Score: 7.4

VulDB Base Score: 6.7
VulDB Temp Score: 6.7
VulDB Vector: 🔍
VulDB Reliability: 🔍

CNA Base Score: 8.2
CNA Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Access control
CWE: CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: No

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

01/21/2022 🔍
06/18/2024 +878 days 🔍
06/18/2024 +0 days 🔍
08/30/2024 +73 days 🔍

Sourcesinfo

Advisory: amd.com
Status: Confirmed

CVE: CVE-2022-23829 (🔍)
GCVE (CVE): GCVE-0-2022-23829
GCVE (VulDB): GCVE-100-268907

Entryinfo

Created: 06/18/2024 21:15
Updated: 08/30/2024 20:45
Changes: 06/18/2024 21:15 (58), 06/19/2024 15:29 (1), 08/30/2024 20:45 (2)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!