Epyc 7003 Firmware vulnerabilitiesRanked by how likely they are to be used.
Epyc 7003 Firmware is made by Amd. We track 34 published vulnerabilities in it, across 8 versions. None of them is on the list of flaws known to be exploited today. If you run Epyc 7003 Firmware, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Epyc 7003 Firmware vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Epyc 7003 Firmware's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Epyc 7003 Firmware flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 1.0%CVE-2020-12988High
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.
- 0.6%CVE-2023-20531High
Insufficient bound checks in the SMU may allow an attacker to update the SRAM from/to address space to an invalid value potentially resulting in a denial of service.
- 0.6%CVE-2023-20529High
Insufficient bound checks in the SMU may allow an attacker to update the from/to address space to an invalid value potentially resulting in a denial of service.
- 0.6%CVE-2023-20530High
Insufficient input validation of BIOS mailbox messages in SMU may result in out-of-bounds memory reads potentially resulting in a denial of service.
- 0.6%CVE-2022-23824Medium
IBPB may not prevent return branch predictions from being specified by pre-IBPB branch targets leading to a potential information disclosure.
- 0.6%CVE-2023-20527Medium
Improper syscall input validation in the ASP Bootloader may allow a privileged attacker to read memory out-of-bounds, potentially leading to a denial-of-service.
- 0.6%CVE-2023-20525Medium
Insufficient syscall input validation in the ASP Bootloader may allow a privileged attacker to read memory outside the bounds of a mapped register potentially leading to a denial of service.
- 0.6%CVE-2023-20532Medium
Insufficient input validation in the SMU may allow an attacker to improperly lock resources, potentially resulting in a denial of service.
- 0.3%CVE-2021-46744Medium
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 ciphertext values over time.
- 0.3%CVE-2020-12966Medium
AMD EPYC™ Processors contain an information disclosure vulnerability in the Secure Encrypted Virtualization with Encrypted State (SEV-ES) and Secure Encrypted Virtualization with Secure Nested Paging (SEV-SNP).
Running Epyc 7003 Firmware? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
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.
- Matched to
- Epyc 7003 Firmware on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 34 published vulnerabilities listed under the name Epyc 7003 Firmware, across 8 versions.
None of Epyc 7003 Firmware's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Epyc 7003 Firmware. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.