dbcve.org
Epyc 7003 FirmwareOperating system · Amd

CVE-2021-26343

MEDIUM · 5.5 CVSS v3.1 Published 2023-01-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Insufficient validation in ASP BIOS and DRTM commands may allow malicious supervisor x86 software to disclose the contents of sensitive memory which may result in information disclosure.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is an AMD Secure Processor (ASP) vulnerability affecting BIOS and DRTM (Dynamic Root of Trust Measurement) commands. Insufficient validation in these commands allows malicious supervisor-level x86 software to read sensitive memory contents that should be protected, leading to information disclosure.

MitigationApply AMD-provided firmware updates for the ASP/BIOS. This is a firmware-level vulnerability requiring a BIOS/firmware update from AMD or the system OEM.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Epyc 7003 FirmwareOperating system
Affected:< milanpi_1.0.0.3
Epyc 72f3 FirmwareOperating system
Affected:< milanpi_1.0.0.3
Epyc 7313 FirmwareOperating system
Affected:< milanpi_1.0.0.3
Epyc 7313p FirmwareOperating system
Affected:< milanpi_1.0.0.3
Epyc 7343 FirmwareOperating system
Affected:< milanpi_1.0.0.3
Epyc 7373x FirmwareOperating system
Affected:< milanpi_1.0.0.3
Epyc 73f3 FirmwareOperating system
Affected:< milanpi_1.0.0.3
Epyc 7413 FirmwareOperating system
Affected:< milanpi_1.0.0.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the AMD Epyc processor model
    Run 'dmidecode -t processor' or 'lscpu' and look for the processor version string. For this CVE, focus on Epyc 7003 series processors including Epyc 72f3, 7313, 7313p, 7343, 7373x, 73f3, and 7413 models.
    Affected if The processor is an AMD Epyc 7003 series model and the firmware version is below milanpi_1.0.0.3
  2. Check the ASP firmware version
    Use the system's BIOS/UEFI setup utility or run 'dmidecode -t bios' to retrieve the BIOS version string. Alternatively, consult the OEM management interface or use AMD's platform management tools if available.
    Affected if The displayed firmware version string is earlier than milanpi_1.0.0.3, or the version cannot be determined but the system is an affected Epyc 7003 model
  3. Verify DRTM is enabled in the system
    Check system BIOS/UEFI settings for Dynamic Root of Trust Measurement (DRTM) configuration options, or examine OS-level DRTM status via 'cat /proc/cmdline' for DRTM-related kernel parameters if applicable.
    Affected if DRTM is enabled on an affected processor, as the vulnerability specifically affects DRTM command processing

A system is affected if it uses an AMD Epyc 7003 series processor (72f3, 7313, 7313p, 7343, 7373x, 73f3, or 7413) with ASP/BIOS firmware versions prior to milanpi_1.0.0.3 and has DRTM or BIOS-level ASP commands accessible to supervisor-level software.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply AMD-provided firmware updates for the ASP/BIOS. This is a firmware-level vulnerability requiring a BIOS/firmware update from AMD or the system OEM.

Recommended fix Moderate confidence

milanpi_1.0.0.3 or later

  1. Obtain the updated BIOS firmware from AMD or your system manufacturer that includes the milanpi_1.0.0.3 or later firmware version
  2. Follow the system manufacturer's instructions for updating the BIOS/UEFI firmware, typically involving flashing the firmware through the BIOS setup utility or a dedicated firmware update tool
  3. After updating, verify that the firmware version has been successfully applied
Caveat Firmware updates carry inherent risks and should be performed carefully following manufacturer guidance; ensure stable power during the update process

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Epyc 7003 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-26343 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-26343 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data