AMD Epyc 74f3 Firmware vulnerabilities

95 CVEs affecting AMD Epyc 74f3 Firmware, 0 known to be exploited (CISA KEV), with EPSS scores. Latest: CVE-2023-20591, published 2024-08-13.

More from AMD.

Highest priority

Known exploited (CISA KEV) first, then by EPSS exploit probability.

• CVE-2023-20569, published 2023-08-08. Medium severity, CVSS 4.7. EPSS: 7.3% chance of exploitation in the next 30 days. A side channel vulnerability on some of the AMD CPUs may allow an attacker to influence the return address prediction. This may result in speculative execution at an attacker-controlled address,…
• CVE-2021-26322, published 2021-11-16. High severity, CVSS 7.5. EPSS: 1% chance of exploitation in the next 30 days. Persistent platform private key may not be protected with a random IV leading to a potential “two time pad attack”.
• CVE-2020-12988, published 2021-06-11. High severity, CVSS 7.5. EPSS: 1% chance of exploitation in the next 30 days. A potential denial of service (DoS) vulnerability exists in the integrated chipset that may allow a malicious attacker to hang the system when it is rebooted.
• CVE-2023-20592, published 2023-11-14. Medium severity, CVSS 6.5. EPSS: 1% chance of exploitation in the next 30 days. Improper or unexpected behavior of the INVD instruction in some AMD CPUs may allow an attacker with a malicious hypervisor to affect cache line write-back behavior of the CPU leading to a potential…
• CVE-2021-26338, published 2021-11-16. High severity, CVSS 7.5. EPSS: 0.9% chance of exploitation in the next 30 days. Improper access controls in System Management Unit (SMU) may allow for an attacker to override performance control tables located in DRAM resulting in a potential lack of system resources.
• CVE-2023-20575, published 2023-07-11. Medium severity, CVSS 6.5. EPSS: 0.8% chance of exploitation in the next 30 days. A potential power side-channel vulnerability in some AMD processors may allow an authenticated attacker to use the power reporting functionality to monitor a program’s execution inside an AMD SEV VM…
• CVE-2023-20520, published 2023-05-09. Critical severity, CVSS 9.8. EPSS: 0.8% chance of exploitation in the next 30 days. Improper access control settings in ASP Bootloader may allow an attacker to corrupt the return address causing a stack-based buffer overrun potentially leading to arbitrary code execution.
• CVE-2021-46769, published 2023-05-09. High severity, CVSS 8.8. EPSS: 0.8% chance of exploitation in the next 30 days. Insufficient syscall input validation in the ASP Bootloader may allow a privileged attacker to execute arbitrary DMA copies, which can lead to code execution.
• CVE-2021-26379, published 2023-05-09. Critical severity, CVSS 9.8. EPSS: 0.7% chance of exploitation in the next 30 days. Insufficient input validation of mailbox data in the SMU may allow an attacker to coerce the SMU to corrupt SMRAM, potentially leading to a loss of integrity and privilege escalation.
• CVE-2021-46756, published 2023-05-09. Critical severity, CVSS 9.1. EPSS: 0.6% chance of exploitation in the next 30 days. Insufficient validation of inputs in SVC_MAP_USER_STACK in the ASP (AMD Secure Processor) bootloader may allow an attacker with a malicious Uapp or ABL to send malformed or invalid syscall to the…

Latest

• CVE-2023-20591, published 2024-08-13. Critical severity, CVSS 10.0. EPSS: 0.3% chance of exploitation in the next 30 days. Improper re-initialization of IOMMU during the DRTM event may permit an untrusted platform configuration to persist, allowing an attacker to read or modify hypervisor memory, potentially resulting in…
• CVE-2023-20584, published 2024-08-13. Medium severity, CVSS 6.0. EPSS: 0.2% chance of exploitation in the next 30 days. IOMMU improperly handles certain special address ranges with invalid device table entries (DTEs), which may allow an attacker with privileges and a compromised Hypervisor to induce DTE faults to…
• CVE-2023-20578, published 2024-08-13. Medium severity, CVSS 6.4. EPSS: 0.1% chance of exploitation in the next 30 days. A TOCTOU (Time-Of-Check-Time-Of-Use) in SMM may allow an attacker with ring0 privileges and access to the BIOS menu or UEFI shell to modify the communications buffer potentially resulting in…
• CVE-2021-26344, published 2024-08-13. High severity, CVSS 8.2. EPSS: 0.2% chance of exploitation in the next 30 days. An out of bounds memory write when processing the AMD PSP1 Configuration Block (APCB) could allow an attacker with access the ability to modify the BIOS image, and the ability to sign the resulting…
• CVE-2024-21980, published 2024-08-05. High severity, CVSS 7.9. EPSS: 0.4% chance of exploitation in the next 30 days. Improper restriction of write operations in SNP firmware could allow a malicious hypervisor to potentially overwrite a guest's memory or UMC seed resulting in loss of confidentiality and integrity.
• CVE-2024-21978, published 2024-08-05. High severity, CVSS 7.9. EPSS: 0.5% chance of exploitation in the next 30 days. Improper input validation in SEV-SNP could allow a malicious hypervisor to read or overwrite guest memory potentially leading to data leakage or data corruption.
• CVE-2023-31355, published 2024-08-05. Medium severity, CVSS 6.0. EPSS: 0.4% chance of exploitation in the next 30 days. Improper restriction of write operations in SNP firmware could allow a malicious hypervisor to overwrite a guest's UMC seed potentially allowing reading of memory from a decommissioned guest.
• CVE-2023-31347, published 2024-02-13. Medium severity, CVSS 4.9. EPSS: 0.5% chance of exploitation in the next 30 days. Due to a code bug in Secure_TSC, SEV firmware may allow an attacker with high privileges to cause a guest to observe an incorrect TSC when Secure TSC is enabled potentially resulting in a loss of…
• CVE-2023-31346, published 2024-02-13. Medium severity, CVSS 6.0. EPSS: 0.3% chance of exploitation in the next 30 days. Failure to initialize memory in SEV Firmware may allow a privileged attacker to access stale data from other guests.
• CVE-2023-20573, published 2024-01-11. Low severity, CVSS 3.2. EPSS: 0.3% chance of exploitation in the next 30 days. A privileged attacker can prevent delivery of debug exceptions to SEV-SNP guests potentially resulting in guests not receiving expected debug information.