CVE-2023-20575: A potential power side-channel vulnerability in some AMD processors may allow an authenticated attacker to use the power reporting…
Noroxi assessment
Priority: Monitor (action score 26/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.80% (FIRST EPSS); higher than 57.3% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
A potential power side-channel vulnerability in some AMD processors may allow an authenticated attacker to use the power reporting functionality to monitor a program’s execution inside an AMD SEV VM potentially resulting in a leak of sensitive information.
- Published
- Jul 11, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.8% · 57th percentile
- CWE
- CWE-203
Report tools
Action score
26
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.8%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| amd | epyc 9274f | cpe:2.3:h:amd:epyc_9274f |
| amd | epyc 9334 firmware | cpe:2.3:o:amd:epyc_9334_firmware |
| amd | epyc 9334 | cpe:2.3:h:amd:epyc_9334 |
| amd | epyc 7251 firmware | cpe:2.3:o:amd:epyc_7251_firmware |
| amd | epyc 7251 | cpe:2.3:h:amd:epyc_7251 |
| amd | epyc 7281 firmware | cpe:2.3:o:amd:epyc_7281_firmware |
| amd | epyc 7281 | cpe:2.3:h:amd:epyc_7281 |
| amd | epyc 7301 firmware | cpe:2.3:o:amd:epyc_7301_firmware |
| amd | epyc 7301 | cpe:2.3:h:amd:epyc_7301 |
| amd | epyc 7351 firmware | cpe:2.3:o:amd:epyc_7351_firmware |
| amd | epyc 7351 | cpe:2.3:h:amd:epyc_7351 |
| amd | epyc 7351p firmware | cpe:2.3:o:amd:epyc_7351p_firmware |
and 164 more
Versions reported by the vendor
Affected version ranges reported by the assigning authority (AMD). Independent of NVD's CPE analysis and usually ahead of it.
AMD 1st Gen AMD EPYC™ Processors
- variousaffected
AMD 2nd Gen AMD EPYC™ Processors
- variousaffected
AMD 3rd Gen AMD EPYC™ Processors
- variousaffected
AMD 4th Gen AMD EPYC™ Processors
- Variousaffected
Affected versions · NVD (20)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- amd epyc 5552 firmwareall versions
- amd epyc 7232p firmwareall versions
- amd epyc 7251 firmwareall versions
- amd epyc 7252 firmwareall versions
- amd epyc 7262 firmwareall versions
- amd epyc 7272 firmwareall versions
- amd epyc 7281 firmwareall versions
- amd epyc 72f3 firmwareall versions
- amd epyc 7301 firmwareall versions
- amd epyc 7302 firmwareall versions
- amd epyc 7302p firmwareall versions
- amd epyc 7313 firmwareall versions
- amd epyc 7313p firmwareall versions
- amd epyc 7343 firmwareall versions
- amd epyc 7351 firmwareall versions
- amd epyc 7351p firmwareall versions
- amd epyc 7352 firmwareall versions
- amd epyc 7373x firmwareall versions
- amd epyc 73f3 firmwareall versions
- amd epyc 7401 firmwareall versions
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-203 · Observable DiscrepancyCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.