dbcve.org
Epyc 7763 FirmwareOperating system · Amd

CVE-2023-20566

HIGH · 7.5 CVSS v3.1 Published 2023-11-14
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
Improper address validation in ASP with SNP enabled may potentially allow an attacker to compromise guest memory 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

This is an AMD processor vulnerability in the AMD Secure Processor (ASP) when Secure Nested Paging (SNP) is enabled. Improper address validation allows a potential attacker to compromise guest memory integrity in virtualized environments using AMD's SEV-SNP technology.

MitigationApply AMD-provided firmware/BIOS updates for the AMD Secure Processor to address the address validation flaw. If immediate patching is not possible, evaluate the risk of disabling SNP or isolating affected hypervisors until patches can be applied.

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 7763 FirmwareOperating system
Affected:< milanpi_1.0.0.b
Epyc 7713p FirmwareOperating system
Affected:< milanpi_1.0.0.b
Epyc 7713 FirmwareOperating system
Affected:< milanpi_1.0.0.b
Epyc 7663p FirmwareOperating system
Affected:< milanpi_1.0.0.b
Epyc 7663 FirmwareOperating system
Affected:< milanpi_1.0.0.b
Epyc 7643p FirmwareOperating system
Affected:< milanpi_1.0.0.b
Epyc 7773x FirmwareOperating system
Affected:< milanpi_1.0.0.b
Epyc 7643 FirmwareOperating system
Affected:< milanpi_1.0.0.b

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

CVSS:3.1/AV:N/AC:L/PR:N/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 the AMD Epyc processor model
    Run 'dmidecode -t processor' or 'cat /proc/cpuinfo' to confirm the processor model is one of the affected variants: Epyc 7763, 7713p, 7713, 7663p, 7663, 7643p, 7773x, or 7643
    Affected if The processor model matches one of the listed affected Epyc variants
  2. Check the AMD Secure Processor firmware version
    Use 'dmidecode' or AMD-specific tools (such as 'asp、制? or platform-specific firmware utilities) to query the AMD Secure Processor firmware version. Compare the firmware version string to 'milanpi_1.0.0.b'
    Affected if The firmware version is present and is lower than 'milanpi_1.0.0.b' (e.g., earlier than 1.0.0.b)
  3. Verify if Secure Nested Paging (SNP) is enabled
    Check the hypervisor or BIOS configuration for SEV-SNP settings. On Linux, this may be inspectable via 'cat /sys/kernel/debug/sev' or hypervisor-specific commands (e.g., 'virsh dominfo <vm>' for libvirt with SEV-SNP flags). Also verify BIOS/UEFI settings for SNP enablement
    Affected if SNP/SEV-SNP is actively enabled in the hypervisor or BIOS configuration

A system is affected if it runs an affected AMD Epyc model with firmware versions prior to milanpi_1.0.0.b AND has Secure Nested Paging (SNP/SEV-SNP) enabled.

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 the AMD Secure Processor to address the address validation flaw. If immediate patching is not possible, evaluate the risk of disabling SNP or isolating affected hypervisors until patches can be applied.

Recommended fix High confidence

milanpi_1.0.0.b or later firmware version for AMD Epyc 7000 series (Milan)

  1. Identify the current firmware version of the AMD Epyc processor by accessing the BMC web interface or using IPMI commands (e.g., `ipmi-fru` or through the server vendor's management tool)
  2. Navigate to www.amd.com and locate the Epyc 7000 series (Milan) firmware downloads section, or obtain the firmware update from your server hardware vendor (Dell, HPE, Lenovo, etc.)
  3. Download the firmware package with version milanpi_1.0.0.b or later that matches your specific Epyc model (e.g., Epyc 7763, 7713p, 7713, etc.)
  4. Access the BMC interface (iRemote Management Controller) or use the vendor's firmware update utility to apply the new firmware
  5. Verify the firmware update was successful by checking the BMC or running `ipmi-fru` to confirm the new firmware version is milanpi_1.0.0.b or later
Caveat Firmware updates typically require a server reboot; ensure planned maintenance window and confirm vendor compatibility before applying

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

Fix this in Epyc 7763 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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