CVE-2023-20573

Description

A flaw was found in AMD hardware using the Secure Encrypted Virtualization – Secure Nested Paging (SEV-SNP) feature. This issue may allow a privileged attacker to prevent the delivery of debug exceptions to SEV-SNP guests, potentially resulting in guests not receiving expected debug information.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score3.23.23.2
Attack VectorLocalLocalLocal
Attack ComplexityLowLowLow
Privileges RequiredHighHighHigh
User InteractionNoneNoneNone
ScopeChangedChangedChanged
ConfidentialityNoneNoneNone
Integrity ImpactLowLowLow
Availability ImpactNoneNoneNone

Vector

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

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

cve.org: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:N/I:L/A:N

Understanding the Weakness (CWE)

Confidentiality

Technical Impact: Read Memory; Read Application Data

Recovering data after erasure or overwriting is possible due to a phenomenon called data remanence. For example, if the same value is written repeatedly to a memory location, the corresponding memory cells can become physically altered to a degree such that even after the original data is erased, that data can still be recovered through physical characterization of the memory cells. Physical properties of hardware devices, such as remanence of magnetic media, residual charge of ROMs/RAMs, or screen burn-in, may still retain sensitive data after a data removal process has taken place and power is removed.

Acknowledgements

Red Hat would like to thank Tom Dohrmann for reporting this issue.

Frequently Asked Questions

Want to get errata notifications? Sign up here.