dbcve.org
Ryzen Pro FirmwareOperating system · Amd

CVE-2018-8932

CRITICAL · 9.0 CVSS v3.0 Published 2018-03-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
99/100
Remediation priority · Urgent
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
The AMD Ryzen and Ryzen Pro processor chips have insufficient access control for the Secure Processor, aka RYZENFALL-2, RYZENFALL-3, and RYZENFALL-4.

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 access control on the AMD Secure Processor in Ryzen and Ryzen Pro chips (RYZENFALL-2, RYZENFALL-3, RYZENFALL-4) allows potential unauthorized code execution within the isolated security co-processor that handles functions like fTPM, Secure Boot, and other platform security features.

MitigationApply AMD-provided firmware/BIOS updates for affected Ryzen and Ryzen Pro processors. Verify Secure Processor functionality post-update to ensure security controls are properly enforced.

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
Ryzen Pro FirmwareOperating system
Affected:all versions
Ryzen FirmwareOperating system
Affected:all versions

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
High
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/C:H/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. Identify the processor model
    Use system information tools (such as 'lspci', 'dmidecode', or Windows System Information) to confirm the CPU is an AMD Ryzen or Ryzen Pro series processor
    Affected if The system does not have an AMD Ryzen or Ryzen Pro processor, as this vulnerability only affects those specific product lines
  2. Check Secure Processor firmware version
    Access the BIOS/UEFI settings during system boot and look for Secure Processor or PSP (Platform Security Processor) firmware version information; alternatively, use AMD-specific diagnostic tools if available
    Affected if The Secure Processor firmware version is older than the AMD-provided patches released for this vulnerability - note that 'all versions' in the affected range means unpatched firmware is vulnerable
  3. Verify fTPM or Secure Boot configuration
    Check BIOS/UEFI settings for fTPM (firmware TPM) and Secure Boot features - these are managed by the AMD Secure Processor and indicate the attack surface
    Affected if fTPM or Secure Boot is enabled, as the vulnerability allows unauthorized code execution within the security co-processor handling these features
  4. Check for AMD security advisory
    Review AMD's security advisories for RYZENFALL-related vulnerabilities (specifically RYZENFALL-2, RYZENFALL-3, RYZENFALL-4) and cross-reference with your system's current firmware version
    Affected if The installed Secure Processor firmware predates the AMD patch release date for this vulnerability or cannot be verified as patched

The user is affected if they have an AMD Ryzen or Ryzen Pro system where the Secure Processor firmware has not been updated to address the insufficient access control vulnerability (CVE-2018-8932), particularly when fTPM or Secure Boot features are in use.

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/BIOS updates for affected Ryzen and Ryzen Pro processors. Verify Secure Processor functionality post-update to ensure security controls are properly enforced.

Recommended fix Moderate confidence

Contact OEM/vendor for latest BIOS/firmware version containing RYZENFALL patches

  1. Contact your motherboard or system manufacturer (OEM) to obtain the latest BIOS/firmware update for your specific AMD Ryzen or Ryzen Pro system
  2. Verify with the manufacturer that the update includes the RYZENFALL-2, RYZENFALL-3, and RYZENFALL-4 security patches
  3. Apply the firmware update following the manufacturer's provided instructions
  4. After updating, verify the Secure Processor firmware version has been updated to a patched release
Caveat Firmware updates carry risk of system boot failure if interrupted; ensure stable power and follow OEM update procedures exactly

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

Fix this in Ryzen Pro Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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