Security readout for executives and security teams
Plain-English summary
CVE-2023-20575 is a confidentiality risk in some AMD EPYC processors. An authenticated attacker may abuse power reporting features to infer activity inside an AMD SEV virtual machine, potentially exposing sensitive information. The issue is most relevant to environments relying on SEV for tenant or workload isolation.
Executive priority
Treat this as a targeted confidentiality risk, not a broad outage risk. Prioritize environments where SEV is relied on for tenant isolation or sensitive workloads, especially multi-tenant hosting or cloud infrastructure on older EPYC generations.
Technical view
The vulnerability is a potential power side channel, classified as CWE-203, affecting various 1st, 2nd, and 3rd Gen AMD EPYC processors. AMD lists 4th Gen EPYC as unaffected. The CVSS 3.1 score is 6.5, with high confidentiality impact and no integrity or availability impact.
Likely exposure
Exposure is likely limited to AMD EPYC hosts using AMD SEV VMs where an authenticated attacker can access relevant power reporting functionality. Highest concern is cloud, hosting, or sensitive virtualization environments using 1st through 3rd Gen EPYC platforms.
Exploitation context
The provided sources do not show active exploitation, and the CVE is not listed as KEV. Exploitation requires authenticated access. The described outcome is observation of VM execution behavior through power reporting, which may leak sensitive information without altering systems.
Researcher notes
Evidence is limited to the CVE record and AMD advisory reference. The source bundle does not provide exploit details, patch specifics, or named configuration mitigations. Validate exposure through hardware generation, SEV usage, and vendor guidance rather than assuming all AMD systems are affected.
Mitigation direction
- Review AMD-SB-3004 for processor-specific vendor guidance.
- Inventory AMD EPYC generations on SEV virtualization hosts.
- Prioritize 1st, 2nd, and 3rd Gen EPYC systems running sensitive SEV workloads.
- Track OEM, BIOS, firmware, and cloud provider guidance for affected platforms.
- Consider workload placement away from affected hosts where confidentiality requirements are strict.
Validation and detection
- Identify hosts running AMD EPYC 1st, 2nd, or 3rd Gen processors.
- Confirm whether AMD SEV is used for sensitive virtual machines.
- Check whether 4th Gen EPYC hosts are used for critical SEV workloads.
- Review platform vendor advisories against installed BIOS and firmware levels.
- Document whether authenticated users can access power reporting functionality.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-203: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2023-20575 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N2.83.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.amd.com/en/corporate/product-security/bulletin/AMD-SB-3004CVE reference · vendor-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Observable Discrepancy
Observable Discrepancy represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.