CVE-2023-20573 | Debug Exception Delivery in Secure Nested Paging

A privileged attacker can prevent delivery of debug exceptions to SEV-SNP guests potentially resulting in guests not receiving expected debug information.

Published: 2024-01-11 Last update: 2025-06-20 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2023-20573 is rated Low Risk (20.2/100): CVSS Low severity, with low exploitation likelihood (EPSS 0.09%). Mandatory action: Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2023-20573

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-03-30 0.94% 0.09% -0.84%
2 2025-03-29 0.09% 0.94% +0.84%
3 2025-03-28 0.09%

Full EPSS history (8 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2023-20573

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
3.2 3.1 LOW
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:N/I:L/A:N Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
1.5 1.4 [email protected]
3.2 3.1 LOW
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:N/I:L/A:N Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
1.5 1.4 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2023-20573

OS Trackers for CVE-2023-20573

vendor priority summary link
redhat low https://access.redhat.com/security/cve/CVE-2023-20573

Affected software / configurations for CVE-2023-20573

Vendor Product Version Raw CPE
amd epyc_7763_firmware cpe:2.3:o:amd:epyc_7763_firmware:-:*:*:*:*:*:*:*
amd epyc_7713p_firmware cpe:2.3:o:amd:epyc_7713p_firmware:-:*:*:*:*:*:*:*
amd epyc_7713_firmware cpe:2.3:o:amd:epyc_7713_firmware:-:*:*:*:*:*:*:*
amd epyc_7663p_firmware cpe:2.3:o:amd:epyc_7663p_firmware:-:*:*:*:*:*:*:*
amd epyc_7663_firmware cpe:2.3:o:amd:epyc_7663_firmware:-:*:*:*:*:*:*:*
amd epyc_7643p_firmware cpe:2.3:o:amd:epyc_7643p_firmware:-:*:*:*:*:*:*:*
amd epyc_7773x_firmware cpe:2.3:o:amd:epyc_7773x_firmware:-:*:*:*:*:*:*:*
amd epyc_7643_firmware cpe:2.3:o:amd:epyc_7643_firmware:-:*:*:*:*:*:*:*
amd epyc_7573x_firmware cpe:2.3:o:amd:epyc_7573x_firmware:-:*:*:*:*:*:*:*
amd epyc_75f3_firmware cpe:2.3:o:amd:epyc_75f3_firmware:-:*:*:*:*:*:*:*
amd epyc_7543p_firmware cpe:2.3:o:amd:epyc_7543p_firmware:-:*:*:*:*:*:*:*
amd epyc_7543_firmware cpe:2.3:o:amd:epyc_7543_firmware:-:*:*:*:*:*:*:*
amd epyc_7513_firmware cpe:2.3:o:amd:epyc_7513_firmware:-:*:*:*:*:*:*:*
amd epyc_7473x_firmware cpe:2.3:o:amd:epyc_7473x_firmware:-:*:*:*:*:*:*:*
amd epyc_7453_firmware cpe:2.3:o:amd:epyc_7453_firmware:-:*:*:*:*:*:*:*
amd epyc_74f3_firmware cpe:2.3:o:amd:epyc_74f3_firmware:-:*:*:*:*:*:*:*
amd epyc_7443p_firmware cpe:2.3:o:amd:epyc_7443p_firmware:-:*:*:*:*:*:*:*
amd epyc_7443_firmware cpe:2.3:o:amd:epyc_7443_firmware:-:*:*:*:*:*:*:*
amd epyc_7413_firmware cpe:2.3:o:amd:epyc_7413_firmware:-:*:*:*:*:*:*:*
amd epyc_7373x_firmware cpe:2.3:o:amd:epyc_7373x_firmware:-:*:*:*:*:*:*:*
amd epyc_73f3_firmware cpe:2.3:o:amd:epyc_73f3_firmware:-:*:*:*:*:*:*:*
amd epyc_7343_firmware cpe:2.3:o:amd:epyc_7343_firmware:-:*:*:*:*:*:*:*
amd epyc_7313p_firmware cpe:2.3:o:amd:epyc_7313p_firmware:-:*:*:*:*:*:*:*
amd epyc_7313_firmware cpe:2.3:o:amd:epyc_7313_firmware:-:*:*:*:*:*:*:*
amd epyc_7303p_firmware cpe:2.3:o:amd:epyc_7303p_firmware:-:*:*:*:*:*:*:*
amd epyc_7303_firmware cpe:2.3:o:amd:epyc_7303_firmware:-:*:*:*:*:*:*:*
amd epyc_72f3_firmware cpe:2.3:o:amd:epyc_72f3_firmware:-:*:*:*:*:*:*:*
amd epyc_7203p_firmware cpe:2.3:o:amd:epyc_7203p_firmware:-:*:*:*:*:*:*:*
amd epyc_7203_firmware cpe:2.3:o:amd:epyc_7203_firmware:-:*:*:*:*:*:*:*
amd epyc_9654p_firmware cpe:2.3:o:amd:epyc_9654p_firmware:-:*:*:*:*:*:*:*
amd epyc_9654_firmware cpe:2.3:o:amd:epyc_9654_firmware:-:*:*:*:*:*:*:*
amd epyc_9634_firmware cpe:2.3:o:amd:epyc_9634_firmware:-:*:*:*:*:*:*:*
amd epyc_9554p_firmware cpe:2.3:o:amd:epyc_9554p_firmware:-:*:*:*:*:*:*:*
amd epyc_9554_firmware cpe:2.3:o:amd:epyc_9554_firmware:-:*:*:*:*:*:*:*
amd epyc_9534_firmware cpe:2.3:o:amd:epyc_9534_firmware:-:*:*:*:*:*:*:*
amd epyc_9474f_firmware cpe:2.3:o:amd:epyc_9474f_firmware:-:*:*:*:*:*:*:*
amd epyc_9454p_firmware cpe:2.3:o:amd:epyc_9454p_firmware:-:*:*:*:*:*:*:*
amd epyc_9454_firmware cpe:2.3:o:amd:epyc_9454_firmware:-:*:*:*:*:*:*:*
amd epyc_9374f_firmware cpe:2.3:o:amd:epyc_9374f_firmware:-:*:*:*:*:*:*:*
amd epyc_9354p_firmware cpe:2.3:o:amd:epyc_9354p_firmware:-:*:*:*:*:*:*:*
amd epyc_9354_firmware cpe:2.3:o:amd:epyc_9354_firmware:-:*:*:*:*:*:*:*
amd epyc_9334_firmware cpe:2.3:o:amd:epyc_9334_firmware:-:*:*:*:*:*:*:*
amd epyc_9274f_firmware cpe:2.3:o:amd:epyc_9274f_firmware:-:*:*:*:*:*:*:*
amd epyc_9254_firmware cpe:2.3:o:amd:epyc_9254_firmware:-:*:*:*:*:*:*:*
amd epyc_9224_firmware cpe:2.3:o:amd:epyc_9224_firmware:-:*:*:*:*:*:*:*
amd epyc_9174f_firmware cpe:2.3:o:amd:epyc_9174f_firmware:-:*:*:*:*:*:*:*
amd epyc_9124_firmware cpe:2.3:o:amd:epyc_9124_firmware:-:*:*:*:*:*:*:*
amd epyc_9684x_firmware cpe:2.3:o:amd:epyc_9684x_firmware:-:*:*:*:*:*:*:*
amd epyc_9384x_firmware cpe:2.3:o:amd:epyc_9384x_firmware:-:*:*:*:*:*:*:*
amd epyc_9184x_firmware cpe:2.3:o:amd:epyc_9184x_firmware:-:*:*:*:*:*:*:*
amd epyc_9754_firmware cpe:2.3:o:amd:epyc_9754_firmware:-:*:*:*:*:*:*:*
amd epyc_9754s_firmware cpe:2.3:o:amd:epyc_9754s_firmware:-:*:*:*:*:*:*:*
amd epyc_9734_firmware cpe:2.3:o:amd:epyc_9734_firmware:-:*:*:*:*:*:*:*
amd epyc_8534p_firmware cpe:2.3:o:amd:epyc_8534p_firmware:-:*:*:*:*:*:*:*
amd epyc_8534pn_firmware cpe:2.3:o:amd:epyc_8534pn_firmware:-:*:*:*:*:*:*:*
amd epyc_8434p_firmware cpe:2.3:o:amd:epyc_8434p_firmware:-:*:*:*:*:*:*:*
amd epyc_8434pn_firmware cpe:2.3:o:amd:epyc_8434pn_firmware:-:*:*:*:*:*:*:*
amd epyc_8324p_firmware cpe:2.3:o:amd:epyc_8324p_firmware:-:*:*:*:*:*:*:*
amd epyc_8324pn_firmware cpe:2.3:o:amd:epyc_8324pn_firmware:-:*:*:*:*:*:*:*
amd epyc_8224p_firmware cpe:2.3:o:amd:epyc_8224p_firmware:-:*:*:*:*:*:*:*
amd epyc_8224pn_firmware cpe:2.3:o:amd:epyc_8224pn_firmware:-:*:*:*:*:*:*:*
amd epyc_8124p_firmware cpe:2.3:o:amd:epyc_8124p_firmware:-:*:*:*:*:*:*:*
amd epyc_8124pn_firmware cpe:2.3:o:amd:epyc_8124pn_firmware:-:*:*:*:*:*:*:*
amd epyc_8024p_firmware cpe:2.3:o:amd:epyc_8024p_firmware:-:*:*:*:*:*:*:*
amd epyc_8024pn_firmware cpe:2.3:o:amd:epyc_8024pn_firmware:-:*:*:*:*:*:*:*

References for CVE-2023-20573

cvelogic Threat Intelligence