dbcve.org
Epyc 7601 FirmwareOperating system · Amd

CVE-2021-26322

HIGH · 7.5 CVSS v3.1 Published 2021-11-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
Persistent platform private key may not be protected with a random IV leading to a potential “two time pad attack”.

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

A persistent platform private key is being protected using encryption without a random Initialization Vector (IV). When the same IV is reused (or a predictable IV is used), encrypting identical plaintexts produces identical ciphertexts, allowing attackers to perform cryptanalysis, detect patterns, and potentially recover plaintext through ciphertext comparison - known as a two-time pad style attack.

MitigationImplement randomized IV generation for all encryption operations of the persistent private key, ensuring each encryption produces a unique IV that is stored alongside the ciphertext. Consider using authenticated encryption modes (like GCM) that inherently require unique IVs.

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 7601 FirmwareOperating system
Affected:< naplespi-sp3_1.0.0.g
Epyc 7551p FirmwareOperating system
Affected:< naplespi-sp3_1.0.0.g
Epyc 7551 FirmwareOperating system
Affected:< naplespi-sp3_1.0.0.g
Epyc 7501 FirmwareOperating system
Affected:< naplespi-sp3_1.0.0.g
Epyc 7451 FirmwareOperating system
Affected:< naplespi-sp3_1.0.0.g
Epyc 7401 FirmwareOperating system
Affected:< naplespi-sp3_1.0.0.g
Epyc 7371 FirmwareOperating system
Affected:< naplespi-sp3_1.0.0.g
Epyc 7351p FirmwareOperating system
Affected:< naplespi-sp3_1.0.0.g

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 -s processor-family' or check /proc/cpuinfo to confirm the exact CPU model (e.g., 7601, 7551p, 7551, 7501, 7451, 7401, 7371, or 7351p)
    Affected if The processor is one of: Epyc 7601, 7551p, 7551, 7501, 7451, 7401, 7371, or 7351p
  2. Check the system firmware version
    Run 'dmidecode -s bios-version' or access the BIOS/UEFI setup to view the firmware version, then compare against 'naplespi-sp3_1.0.0.g'
    Affected if The firmware version is earlier than naplespi-sp3_1.0.0.g (e.g., naplespi-sp3_0.x.x or any version lacking the 'g' revision)
  3. Verify if platform private key storage is in use
    Examine the system for stored platform keys: on Linux check /root/.ssh/ or certificate stores, or review any TPM/secure key storage configurations using 'tpmtool getkey' or vendor tools
    Affected if Platform private keys are stored on the system and were provisioned using the affected firmware versions
  4. Inspect the key encryption mechanism
    If keys exist, use vendor-provided key management tools or analyze the stored key blobs to determine if they were encrypted without randomized IVs (identical plaintext produces identical ciphertext)
    Affected if Encrypted platform keys show patterns indicating reuse of encryption IVs across multiple key installations

A user is affected if they have an AMD Epyc 7000 series processor (specifically 7601, 7551p, 7551, 7501, 7451, 7401, 7371, or 7351p) running firmware version earlier than naplespi-sp3_1.0.0.g and have platform private keys stored that may have been encrypted without proper IV randomization.

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

Implement randomized IV generation for all encryption operations of the persistent private key, ensuring each encryption produces a unique IV that is stored alongside the ciphertext. Consider using authenticated encryption modes (like GCM) that inherently require unique IVs.

Recommended fix Moderate confidence

naplespi-sp3_1.0.0.g or later

  1. 1. Identify the current firmware version of the affected AMD Epyc processor (7601, 7551p, 7551, 7501, 7451, 7401, 7371, or 7351p) using the system management interface or BIOS/firmware update utility.
  2. 2. Navigate to the AMD support website (www.amd.com) or the OEM server manufacturer support portal to obtain the firmware update.
  3. 3. Download the naplespi-sp3_1.0.0.g firmware update or later version specifically for your Epyc processor model.
  4. 4. Apply the firmware update following the standard BMC/BIOS firmware update procedure for your server platform (this typically requires administrator/root privileges and may require a system reboot).
  5. 5. After the update completes, verify the firmware version has been successfully updated to naplespi-sp3_1.0.0.g or later.
  6. 6. Confirm the platform private key is now protected with a random initialization vector (IV) as per the security fix.
Caveat Firmware updates carry inherent risks; ensure proper backups and follow vendor update procedures to avoid system unavailability during the update process

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

Fix this in Epyc 7601 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-26322 — 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-26322 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