AMD EPYC Server/Ryzen/Ryzen Pro/Ryzen Mobile Hardware Validated Boot MASTERKEY input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.0 | $25k-$100k | 0.00 |
Summary
A vulnerability was found in AMD EPYC Server, Ryzen, Ryzen Pro and Ryzen Mobile. It has been rated as very critical. Impacted is an unknown function of the component Hardware Validated Boot. Performing a manipulation results in input validation (MASTERKEY). This vulnerability was named CVE-2018-8930. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability, which was classified as very critical, was found in AMD EPYC Server, Ryzen, Ryzen Pro and Ryzen Mobile (version unknown). This affects an unknown function of the component Hardware Validated Boot. The manipulation with an unknown input leads to a input validation vulnerability (MASTERKEY). CWE is classifying the issue as CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
The AMD EPYC Server, Ryzen, Ryzen Pro, and Ryzen Mobile processor chips have insufficient enforcement of Hardware Validated Boot, aka MASTERKEY-1, MASTERKEY-2, and MASTERKEY-3.
The bug was discovered 03/13/2018. The weakness was presented 03/22/2018 (Website). The advisory is shared at amdflaws.com. This vulnerability is uniquely identified as CVE-2018-8930 since 03/22/2018. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $25k-$100k at the moment (estimation calculated on 01/16/2020).
The vulnerability was handled as a non-public zero-day exploit for at least 9 days. During that time the estimated underground price was around $100k and more. The commercial vulnerability scanner Qualys is able to test this issue with plugin 370876 (AMD Processors Multiple Security Vulnerabilities (RYZENFALL/MASTERKEY/CHIMERA-FW/FALLOUT)).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
See VDB-114934, VDB-114935, VDB-114936 and VDB-114937 for similar entries. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 9.0VulDB Meta Temp Score: 9.0
VulDB Base Score: 9.0
VulDB Temp Score: 9.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.0
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Name: MASTERKEYClass: Input validation / MASTERKEY
CWE: CWE-20
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
03/13/2018 🔍03/22/2018 🔍
03/22/2018 🔍
03/22/2018 🔍
03/23/2018 🔍
01/16/2020 🔍
Sources
Advisory: amdflaws.comStatus: Not defined
Confirmation: 🔍
CVE: CVE-2018-8930 (🔍)
GCVE (CVE): GCVE-0-2018-8930
GCVE (VulDB): GCVE-100-114933
See also: 🔍
Entry
Created: 03/23/2018 10:08Updated: 01/16/2020 08:04
Changes: 03/23/2018 10:08 (60), 01/16/2020 08:04 (2)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.