| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in AMD EPYC. It has been classified as problematic. This vulnerability affects the function SVC_LOAD_FW_IMAGE_BY_INSTANCE/SVC_LOAD_BINARY_BY_ATTRIB of the component Bootloader. This manipulation causes input validation.
This vulnerability is tracked as CVE-2021-26370. No exploit exists.
Upgrading the affected component is recommended.
Details
A vulnerability classified as problematic was found in AMD EPYC (unknown version). Affected by this vulnerability is the function SVC_LOAD_FW_IMAGE_BY_INSTANCE/SVC_LOAD_BINARY_BY_ATTRIB of the component Bootloader. The manipulation with an unknown input 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 integrity, and availability.
The weakness was disclosed 05/11/2022. The advisory is shared at amd.com. This vulnerability is known as CVE-2021-26370 since 01/29/2021. Technical details are known, but no exploit is available.
Upgrading eliminates this vulnerability.
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: 5.5VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: 🔍
Exploiting
Class: Input validationCWE: CWE-20
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Timeline
01/29/2021 🔍05/11/2022 🔍
05/11/2022 🔍
05/13/2022 🔍
Sources
Advisory: amd.comStatus: Confirmed
CVE: CVE-2021-26370 (🔍)
GCVE (CVE): GCVE-0-2021-26370
GCVE (VulDB): GCVE-100-199477
Entry
Created: 05/11/2022 10:13Updated: 05/13/2022 14:39
Changes: 05/11/2022 10:13 (37), 05/13/2022 14:39 (1)
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.