AMD Radeon RX 6000 Graphics Cards PMFW hard-coded key

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.
1.9$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as problematic, was found in AMD Radeon RX 6000 Graphics Cards and Radeon PRO W6000 Graphics Cards. This issue affects some unknown processing of the component PMFW. Such manipulation leads to hard-coded key. This vulnerability is listed as CVE-2023-20512. The attack must be carried out locally. There is no available exploit. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in AMD Radeon RX 6000 Graphics Cards and Radeon PRO W6000 Graphics Cards (affected version not known) and classified as problematic. Affected by this issue is some unknown functionality of the component PMFW. The manipulation with an unknown input leads to a hard-coded key vulnerability. Using CWE to declare the problem leads to CWE-321. The use of a hard-coded cryptographic key significantly increases the possibility that encrypted data may be recovered. Impacted is confidentiality. CVE summarizes:

A hardcoded AES key in PMFW may result in a privileged attacker gaining access to the key, potentially resulting in internal debug information leakage.

The advisory is shared for download at amd.com. This vulnerability is handled as CVE-2023-20512 since 10/27/2022. The exploitation is known to be difficult. The attack needs to be approached locally. Additional levels of successful authentication are necessary for exploitation. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1600.001.

Upgrading eliminates this vulnerability.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Vendor

Name

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 1.9
VulDB Meta Temp Score: 1.9

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

CNA Base Score: 1.9
CNA Vector (AMD): 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Hard-coded key
CWE: CWE-321 / CWE-320
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: Upgrade
Status: 🔍

0-Day Time: 🔍

Timelineinfo

10/27/2022 🔍
08/13/2024 +656 days 🔍
08/13/2024 +0 days 🔍
10/31/2024 +79 days 🔍

Sourcesinfo

Advisory: amd.com
Status: Confirmed

CVE: CVE-2023-20512 (🔍)
GCVE (CVE): GCVE-0-2023-20512
GCVE (VulDB): GCVE-100-274388

Entryinfo

Created: 08/13/2024 19:09
Updated: 10/31/2024 01:50
Changes: 08/13/2024 19:09 (62), 10/31/2024 01:50 (1)
Complete: 🔍
Cache ID: 216::103

Once again VulDB remains the best source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you need the next level of professionalism?

Upgrade your account now!