AMD Ryzen up to 2017-01-27 AGESA Microcode FMA3 Instruction input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.5 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in AMD Ryzen up to 2017-01-27. The affected element is an unknown function of the component AGESA Microcode. This manipulation as part of FMA3 Instruction causes input validation. This vulnerability appears as CVE-2017-7262. The attack requires local access. There is no available exploit. This vulnerability is historically significant due to its background and the way it was received.
Details
A vulnerability classified as critical was found in AMD Ryzen up to 2017-01-27. Affected by this vulnerability is an unknown functionality of the component AGESA Microcode. The manipulation as part of a FMA3 Instruction leads to a input validation vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect availability. The summary by CVE is:
The AMD Ryzen processor with AGESA microcode through 2017-01-27 allows local users to cause a denial of service (system hang) via an application that makes a long series of FMA3 instructions, as demonstrated by the Flops test suite.
The bug was discovered 03/24/2017. The weakness was presented 03/25/2017 (Website). The advisory is shared at forum.hwbot.org. This vulnerability is known as CVE-2017-7262 since 03/24/2017. An attack has to be approached locally. The successful exploitation needs a single authentication. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 09/14/2020). Due to its background and reception, this vulnerability has a historic impact.
The problem might be mitigated by replacing the product with Intel as an alternative.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 97098†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.5
VulDB Base Score: 5.5
VulDB Temp Score: 5.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.5
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
Class: Input validationCWE: CWE-20
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Alternative: Intel
Timeline
03/24/2017 🔍03/24/2017 🔍
03/24/2017 🔍
03/24/2017 🔍
03/25/2017 🔍
03/25/2017 🔍
09/14/2020 🔍
Sources
Advisory: forum.hwbot.orgStatus: Not defined
CVE: CVE-2017-7262 (🔍)
GCVE (CVE): GCVE-0-2017-7262
GCVE (VulDB): GCVE-100-98533
SecurityFocus: 97098 - AMD Ryzen Processor CVE-2017-7262 Local Denial of Service Vulnerability
OSVDB: - CVE-2017-7262 - AMD - Ryzen - Denial of Service Issue
Entry
Created: 03/25/2017 20:51Updated: 09/14/2020 10:03
Changes: 03/25/2017 20:51 (61), 09/14/2020 10:03 (4)
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.