| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 2.5 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in AMD EPYC. This affects an unknown function. The manipulation leads to channel accessible. This vulnerability is referenced as CVE-2021-46744. No exploit is available. It is recommended to upgrade the affected component.
Details
A vulnerability was found in AMD EPYC (version now known) and classified as problematic. This issue affects some unknown processing. The manipulation with an unknown input leads to a channel accessible vulnerability. Using CWE to declare the problem leads to CWE-300. The product does not adequately verify the identity of actors at both ends of a communication channel, or does not adequately ensure the integrity of the channel, in a way that allows the channel to be accessed or influenced by an actor that is not an endpoint. Impacted is confidentiality.
The weakness was published 05/12/2022. The advisory is shared at amd.com. The identification of this vulnerability is CVE-2021-46744 since 03/31/2022. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1557 for this issue.
Upgrading eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 2.6VulDB Meta Temp Score: 2.5
VulDB Base Score: 2.6
VulDB Temp Score: 2.5
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: Channel accessibleCWE: CWE-300
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
03/31/2022 🔍05/12/2022 🔍
05/12/2022 🔍
05/14/2022 🔍
Sources
Advisory: amd.comStatus: Confirmed
CVE: CVE-2021-46744 (🔍)
GCVE (CVE): GCVE-0-2021-46744
GCVE (VulDB): GCVE-100-199625
Entry
Created: 05/12/2022 12:00Updated: 05/14/2022 13:49
Changes: 05/12/2022 12:00 (35), 05/12/2022 12:01 (1), 05/14/2022 13:49 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.