dbcve.org
Epyc 7773x FirmwareOperating system · Amd

CVE-2021-26354

MEDIUM · 5.5 CVSS v3.1 Published 2023-05-09
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 bounds checking in ASP may allow an attacker to issue a system call from a compromised ABL which may cause arbitrary memory values to be initialized to zero, potentially leading to a loss of integrity.

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

Insufficient bounds checking in ASP (Application Support Process) on HP NonStop systems allows a compromised ABL (Advanced Business Language) program to issue system calls that initialize arbitrary memory values to zero, causing a loss of integrity.

MitigationApply vendor patches for CVE-2021-26354 to the NonStop kernel ASP component. Review and recompile any ABL applications to ensure compatibility with the patched environment.

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 7773x FirmwareOperating system
Affected:< milanpi_1.0.0.6
Epyc 7763 FirmwareOperating system
Affected:< milanpi_1.0.0.6
Epyc 7713p FirmwareOperating system
Affected:< milanpi_1.0.0.6
Epyc 7713 FirmwareOperating system
Affected:< milanpi_1.0.0.6
Epyc 7663 FirmwareOperating system
Affected:< milanpi_1.0.0.6
Epyc 7643 FirmwareOperating system
Affected:< milanpi_1.0.0.6
Epyc 75f3 FirmwareOperating system
Affected:< milanpi_1.0.0.6
Epyc 7573x FirmwareOperating system
Affected:< milanpi_1.0.0.6

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
None
Integrity
High
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 system platform
    Verify the system is running HP NonStop. This may require checking system documentation, running 'version' or 'sysgen' commands, or consulting system inventory records.
    Affected if System is not HP NonStop - the vulnerability does not apply to other platforms
  2. Identify AMD Epyc processor model
    Check the installed AMD Epyc processor model on the NonStop system. This may be available via system inventory, hardware management tools, or BIOS/UEFI configuration.
    Affected if Processor is not one of: Epyc 7773x, 7763, 7713p, 7713, 7663, 7643, 75f3, or 7573x - these are the only affected models
  3. Check AMD Epyc firmware version
    Retrieve the current firmware version of the AMD Epyc processor. This typically requires accessing the BMC/IPMI interface, BIOS management interface, or using vendor-specific firmware version checking tools appropriate for the HP NonStop platform.
    Affected if Firmware version is earlier than milanpi_1.0.0.6 - versions below this threshold are affected
  4. Verify ASP component status
    Determine if the Application Support Process (ASP) component is enabled and running on the NonStop system. Check for ASP processes via system management interfaces or process listing tools.
    Affected if ASP is not present or not active - the vulnerability requires ASP to be functioning for the attack vector to apply

System is affected if it runs HP NonStop on an AMD Epyc processor from the affected list with firmware version earlier than milanpi_1.0.0.6, and the ASP component is present and active.

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 vendor patches for CVE-2021-26354 to the NonStop kernel ASP component. Review and recompile any ABL applications to ensure compatibility with the patched environment.

Recommended fix Moderate confidence

milanpi_1.0.0.6 or later firmware for AMD Epyc 7000 series (Milan) processors

  1. Verify the current firmware version of the AMD Epyc processor using system management tools or BIOS information
  2. Download the latest firmware update for the specific Epyc model from the official AMD website or your server vendor's support page
  3. Ensure the firmware version is milanpi_1.0.0.6 or later (which contains the fix for CVE-2021-26354)
  4. Follow your server vendor's standard firmware update procedure, which typically involves: a) backing up current configuration, b) staging the firmware update file, c) applying the update through BMC/BIOS update utility, d) rebooting the system
  5. After update, verify the new firmware version is correctly installed and matches the fixed release
Caveat Firmware updates carry risk; ensure proper backups and follow vendor procedures to avoid rendering the system non-functional

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

Fix this in Epyc 7773x Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing24.0 h
  • Review / QA12.0 h
60.0 hours of engineering $10,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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