dbcve.org
Romepi FirmwareOperating system · Amd

CVE-2021-46779

HIGH · 7.1 CVSS v3.1 Published 2023-01-11
Fix available
A fix is available. Upgrade to 1.0.0.c / 1.0.0.g or later.
See remediation →
73/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 input validation in SVC_ECC_PRIMITIVE system call in a compromised user application or ABL may allow an attacker to corrupt ASP (AMD Secure Processor) OS memory which may lead to potential loss of integrity and availability.

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 input validation in the SVC_ECC_PRIMITIVE system call within the AMD Secure Processor (ASP) allows a compromised user application or malicious ABL (AMD Boot Loader) to corrupt ASP OS memory, potentially leading to loss of integrity and availability of the secure processing environment.

MitigationApply AMD-provided firmware updates for the AMD Secure Processor; ensure the ABL is sourced from trusted, signed AMD sources; restrict privileged access to prevent compromised applications from reaching the vulnerable system call.

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
Romepi FirmwareOperating system
Affected:< 1.0.0.c
Milanpi FirmwareOperating system
Affected:< 1.0.0.4
Naplespi FirmwareOperating system
Affected:< 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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

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

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. Confirm AMD Secure Processor presence
    Check if the system uses an AMD processor with a Secure Processor subsystem. On Linux, run 'lspci | grep -i amd' or check /proc/cpuinfo for AMD processor information. The ASP is a hardware component in AMD processors.
    Affected if System does not have an AMD processor with Secure Processor, then not affected
  2. Identify the AMD platform family
    Determine if the system is based on Romepi, Milanpi, or Naplespi architecture. This can be found via 'cat /proc/cpuinfo' showing the CPU model, or using 'dmidecode -t processor' to get the exact AMD CPU family and model designation.
    Affected if System is not an AMD Rome, Milan, or Naples processor family - different vulnerability context applies
  3. Retrieve ASP firmware version
    Access the AMD Secure Processor firmware version through platform-specific methods. On Linux systems with AMD PSP driver loaded, check /dev/pts/ or use 'dmesg | grep -i asp' to find firmware version logs. The version string may appear as 'Romepi', 'Milanpi', or 'Naplespi' followed by a version number.
    Affected if Cannot retrieve the ASP firmware version from system logs or drivers - manual verification may be required
  4. Compare firmware version to affected ranges
    For Romepi platforms: verify if version is less than 1.0.0.c. For Milanpi: verify if version is less than 1.0.0.4. For Naplespi: verify if version is less than 1.0.0.g. Use exact string comparison as version schemes are alphanumeric.
    Affected if Firmware version is below the specified threshold for your specific platform family

The environment is affected if it contains an AMD processor with Secure Processor firmware version lower than 1.0.0.c (Romepi), 1.0.0.4 (Milanpi), or 1.0.0.g (Naplespi).

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
Upgrade available Upgrade to 1.0.0.c / 1.0.0.g / 1.0.0.4 or later
Fixed in 1.0.0.c1.0.0.g1.0.0.4
Interim mitigation

Apply AMD-provided firmware updates for the AMD Secure Processor; ensure the ABL is sourced from trusted, signed AMD sources; restrict privileged access to prevent compromised applications from reaching the vulnerable system call.

Recommended fix High confidence

Romepi: 1.0.0.c | Milanpi: 1.0.0.4 | Naplespi: 1.0.0.g

  1. 1. Identify the specific platform (Romepi, Milanpi, or Naplespi) in use
  2. 2. Determine the current firmware version by accessing the system management interface or using AMD's firmware diagnostic tools
  3. 3. Download the latest firmware from AMD's official support website (www.amd.com) for the identified platform
  4. 4. Review AMD's firmware update instructions and ensure the system meets all prerequisites
  5. 5. Apply the firmware update: upgrade Romepi to version 1.0.0.c or later; upgrade Milanpi to version 1.0.0.4 or later; upgrade Naplespi to version 1.0.0.g or later
  6. 6. Verify the firmware update was successful by confirming the new version number
  7. 7. Reboot the system as required by the firmware update process
Caveat Firmware upgrades carry inherent risk and should be performed carefully; ensure power stability during the update process

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

Fix this in Romepi Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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