CVE-2023-20597: Improper initialization of variables in the DXE driver may allow a privileged user to leak sensitive information via local access.
Noroxi assessment
Priority: Monitor (action score 22/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.18% (FIRST EPSS).
- Someone with local access to the system 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
- Published
- Sep 20, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- CWE-824
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
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 | ryzen 3900 | cpe:2.3:h:amd:ryzen_3900 |
| amd | ryzen 3 3100 firmware | cpe:2.3:o:amd:ryzen_3_3100_firmware |
| amd | ryzen 3 3100 | cpe:2.3:h:amd:ryzen_3_3100 |
| amd | ryzen 3 3200g firmware | cpe:2.3:o:amd:ryzen_3_3200g_firmware |
| amd | ryzen 3 3200g | cpe:2.3:h:amd:ryzen_3_3200g |
| amd | ryzen 3 3200ge firmware | cpe:2.3:o:amd:ryzen_3_3200ge_firmware |
| amd | ryzen 3 3200ge | cpe:2.3:h:amd:ryzen_3_3200ge |
| amd | ryzen 3 3200u firmware | cpe:2.3:o:amd:ryzen_3_3200u_firmware |
| amd | ryzen 3 3200u | cpe:2.3:h:amd:ryzen_3_3200u |
| amd | ryzen 3 3250c firmware | cpe:2.3:o:amd:ryzen_3_3250c_firmware |
| amd | ryzen 3 3250c | cpe:2.3:h:amd:ryzen_3_3250c |
| amd | ryzen 3 3250u firmware | cpe:2.3:o:amd:ryzen_3_3250u_firmware |
and 188 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 AMD EPYC™ Embedded 7003
- EmbMilanPI-SP3 1.0.0.6not affected
AMD AMD Ryzen™ Embedded 5000
- EmbAM4PI 1.0.0.2not affected
AMD AMD Ryzen™ Embedded V2000
- EmbeddedPI-FP6 1.0.0.8not affected
AMD AMD Ryzen™ Embedded V3000
- EmbeddedPI-FP7r2 1.0.0.4not affected
AMD Ryzen™ 3000 Series Desktop Processors “Matisse”
- variousaffected
AMD Ryzen™ 5000 Series Desktop Processor with Radeon™ Graphics “Cezanne”
- variousaffected
AMD Ryzen™ 5000 Series Desktop Processors “Vermeer”
- variousaffected
AMD Ryzen™ 5000 Series Mobile Processors with Radeon™ Graphics "Barcelo"
- variousaffected
AMD Ryzen™ 6000 Series Mobile Processors with Radeon™ Graphics "Rembrandt"
- variousaffected
AMD Ryzen™ 7030 Series Mobile Processors with Radeon™ Graphics “Barcelo-R”
- variousaffected
AMD Ryzen™ 7035 Series Mobile Processors with Radeon™ Graphics "Rembrandt-R"
- variousaffected
AMD Ryzen™ Threadripper™ 3000 Series Processors “Castle Peak” HEDT
- 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 ryzen 3 3100 firmwarecomboam4pi_1.0.0.9
- amd ryzen 3 3100 firmwarecomboam4v2pi_1.2.0.8
- amd ryzen 3 3200g firmwarecomboam4pi_1.0.0.9
- amd ryzen 3 3200g firmwarecomboam4v2pi_1.2.0.8
- amd ryzen 3 3200ge firmwarecomboam4pi_1.0.0.9
- amd ryzen 3 3200ge firmwarecomboam4v2pi_1.2.0.8
- amd ryzen 3 3200u firmwarecomboam4pi_1.0.0.9
- amd ryzen 3 3200u firmwarecomboam4v2pi_1.2.0.8
- amd ryzen 3 3250c firmwarecomboam4pi_1.0.0.9
- amd ryzen 3 3250c firmwarecomboam4v2pi_1.2.0.8
- amd ryzen 3 3250u firmwarecomboam4pi_1.0.0.9
- amd ryzen 3 3250u firmwarecomboam4v2pi_1.2.0.8
- amd ryzen 3 3300 firmwarecomboam4pi_1.0.0.9
- amd ryzen 3 3300 firmwarecomboam4v2pi_1.2.0.8
- amd ryzen 3 3300g firmwarecomboam4pi_1.0.0.9
- amd ryzen 3 3300g firmwarecomboam4v2pi_1.2.0.8
- amd ryzen 3 3300u firmwarecomboam4pi_1.0.0.9
- amd ryzen 3 3300u firmwarecomboam4v2pi_1.2.0.8
- amd ryzen 3 3300x firmwarecomboam4pi_1.0.0.9
- amd ryzen 3 3300x firmwarecomboam4v2pi_1.2.0.8
Same product
amd: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-26346Failure to validate the integer operand in ASP (AMD Secure Processor) bootloader may allow an attacker to introduce an integer overflow in…22Monitor
- CVE-2021-26351Insufficient DRAM address validation in System Management Unit (SMU) may result in a DMA (Direct Memory Access) read/write from/to invalid…22Monitor
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
- Someone with local access to the system 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
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-824 · Access of Uninitialized PointerCVSS vector
CVSS:3.1/AV:L/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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
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.