epyc 7003 firmware · threatengine.sh

Home/Product/amd epyc 7003 firmware

Product

amd epyc 7003 firmware

34 known vulnerabilities across versions

Vulnerabilities are listed by affected version. Select any CVE for the full briefing and its intelligence graph.

Sort Min CVSS Published since

Improper initialization of variables in the DXE driver may allow a privileged user to leak sensitive information via local access.

< milanpi_1.0.0.6

A compromised or malicious ABL or UApp could send a SHA256 system call to the bootloader, which may result in exposure of ASP memo

< milanpi_1.0.0.6

Insufficient bounds checking in ASP may allow an attacker to issue a system call from a compromised ABL which may cause arbitrary

< milanpi_1.0.0.5

Insufficient input validation in the SMU may allow an attacker to improperly lock resources, potentially resulting in a denial of

< milanpi_1.0.0.5

Insufficient bound checks in the SMU may allow an attacker to update the SRAM from/to address space to an invalid value potentiall

< milanpi_1.0.0.5

Insufficient input validation of BIOS mailbox messages in SMU may result in out-of-bounds memory reads potentially resulting in a

< milanpi_1.0.0.5

Insufficient bound checks in the SMU may allow an attacker to update the from/to address space to an invalid value potentially res

< milanpi_1.0.0.5

Insufficient input validation in the SMU may allow a physical attacker to exfiltrate SMU memory contents over the I2C bus potentia

< milanpi_1.0.0.5

Improper syscall input validation in the ASP Bootloader may allow a privileged attacker to read memory out-of-bounds, potentially

< milanpi_1.0.0.5

Insufficient syscall input validation in the ASP Bootloader may allow a privileged attacker to read memory outside the bounds of a

< milanpi_1.0.0.5

TOCTOU in the ASP may allow a physical attacker to write beyond the buffer bounds, potentially leading to a loss of integrity or d

< milanpi-sp3_1.0.0.9

Improper input validation and bounds checking in SEV firmware may leak scratch buffer bytes leading to potential information discl

< milanpi_1.0.0.4

Insufficient bounds checking in ASP (AMD Secure Processor) firmware while handling BIOS mailbox commands, may allow an attacker to

< milanpi_1.0.0.4

Insufficient input validation in SYS_KEY_DERIVE system call in a compromised user application or ABL may allow an attacker to corr

< milanpi-sp3_1.0.0.9

Insufficient validation of address mapping to IO in ASP (AMD Secure Processor) may result in a loss of memory integrity in the SNP

< milanpi-sp3_1.0.0.7

Insufficient fencing and checks in System Management Unit (SMU) may result in access to invalid message port registers that could

< milanpi_1.0.0.3

Insufficient validation in ASP BIOS and DRTM commands may allow malicious supervisor x86 software to disclose the contents of sens

< milanpi_1.0.0.8

Failure to verify the mode of CPU execution at the time of SNP_INIT may lead to a potential loss of memory integrity for SNP guest

< milanpi-sp3_1.0.0.8

Failure to validate the communication buffer and communication service in the BIOS may allow an attacker to tamper with the buffer

IBPB may not prevent return branch predictions from being specified by pre-IBPB branch targets leading to a potential information

Execution unit scheduler contention may lead to a side channel vulnerability found on AMD CPU microarchitectures codenamed “Zen

An attacker with access to a malicious hypervisor may be able to infer data values used in a SEV guest on AMD CPUs by monitoring c

< milanpi-sp3_1.0.0.5

AMD EPYC™ Processors contain an information disclosure vulnerability in the Secure Encrypted Virtualization with Encrypted State

< milanpi-sp3_1.0.0.4

Insufficient DRAM address validation in System Management Unit (SMU) may result in a DMA read from invalid DRAM address to SRAM re

< milanpi-sp3_1.0.0.4

Insufficient bounds checking in System Management Unit (SMU) may cause invalid memory accesses/updates that could result in SMU ha

< milanpi-sp3_1.0.0.4

Improper input and range checking in the AMD Secure Processor (ASP) boot loader image header may allow an attacker to use attacker

< milanpi-sp3_1.0.0.4

AMD System Management Unit (SMU) contains a potential issue where a malicious user may be able to manipulate mailbox entries leadi

< milanpi-sp3_1.0.0.4

AMD System Management Unit (SMU) may experience a heap-based overflow which may result in a loss of resources.

< milanpi-sp3_1.0.0.4

Insufficient validation of guest context in the SNP Firmware could lead to a potential loss of guest confidentiality.

< milanpi-sp3_1.0.0.4

When the AMD Platform Security Processor (PSP) boot rom loads, authenticates, and subsequently decrypts an encrypted FW, due to in

< milanpi-sp3_1.0.0.4

A potential vulnerability exists in AMD Platform Security Processor (PSP) that may allow an attacker to zero any privileged regist

< milanpi-sp3_1.0.0.4

A side effect of an integrated chipset option may be able to be used by an attacker to bypass SPI ROM protections, allowing unauth

< milanpi-sp3_1.0.0.4

Race condition in ASP firmware could allow less privileged x86 code to perform ASP SMM (System Management Mode) operations.

< milanpi-sp3_1.0.0.4

A potential denial of service (DoS) vulnerability exists in the integrated chipset that may allow a malicious attacker to hang the

Vulnerabilities
CISA KEV catalog
CWE weaknesses
CAPEC attack patterns
Package vulnerabilities

Threat intelligence
Threat actors
Tools & malware
ATT&CK techniques
IOCs

Detection & defense
Sigma rules
YARA rules
Atomic Red Team tests
D3FEND countermeasures

Compliance
NIST 800-53
ISO 27001:2022
SOC 2 TSC
PCI-DSS v4.0
CIS Controls v8.1

About
All capabilities
Live statistics
Data sources
Privacy policy
Terms of service

threatengine.sh · Open-source threat intelligence platform · 100+ authoritative sources · Every fact traces to its origin