CVE-2023-20578: A TOCTOU (Time-Of-Check-Time-Of-Use) in SMM may allow an attacker with ring0 privileges and access to the BIOS menu or UEFI shell to modify…
Noroxi assessment
Priority: Monitor (action score 25/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.11% (FIRST EPSS).
- Someone with local access to the system can trigger it. Administrator privileges are required. No user action is required. Special conditions such as timing or configuration are required.
- 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 TOCTOU (Time-Of-Check-Time-Of-Use) in SMM may allow an attacker with ring0 privileges and access to the BIOS menu or UEFI shell to modify the communications buffer potentially resulting in arbitrary code execution.
- Published
- Aug 13, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 1th percentile
- CWE
- CWE-367
Report tools
Action score
25
Low priority for now.
- CVSS
- 25 / 40 · 6.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 6.4
- CNA · AMD
- 7.5
- 1.1 point gap
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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 8024pn firmware | cpe:2.3:o:amd:epyc_8024pn_firmware |
| amd | epyc 8024pn | cpe:2.3:h:amd:epyc_8024pn |
| amd | epyc 8024p firmware | cpe:2.3:o:amd:epyc_8024p_firmware |
| amd | epyc 8024p | cpe:2.3:h:amd:epyc_8024p |
| amd | epyc 8124pn firmware | cpe:2.3:o:amd:epyc_8124pn_firmware |
| amd | epyc 8124pn | cpe:2.3:h:amd:epyc_8124pn |
| amd | epyc 8124p firmware | cpe:2.3:o:amd:epyc_8124p_firmware |
| amd | epyc 8124p | cpe:2.3:h:amd:epyc_8124p |
| amd | epyc 8224pn firmware | cpe:2.3:o:amd:epyc_8224pn_firmware |
| amd | epyc 8224pn | cpe:2.3:h:amd:epyc_8224pn |
| amd | epyc 8224p firmware | cpe:2.3:o:amd:epyc_8224p_firmware |
| amd | epyc 8224p | cpe:2.3:h:amd:epyc_8224p |
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™ 7001 Processors
- NaplesPI 1.0.0.Knot affected
AMD AMD EPYC™ 7002 Processors
- RomePI 1.0.0.Gnot affected
AMD AMD EPYC™ 7003 Processors
- MilanPI 1.0.0.Bnot affected
AMD AMD EPYC™ 9004 Processors
- GenoaPI 1.0.0.2not affected
AMD AMD EPYC™ Embedded 3000
- SnowyOwl PI 1.1.0.Anot affected
AMD AMD EPYC™ Embedded 7002
- EmbRomePI-SP3 1.0.0.Anot affected
AMD AMD EPYC™ Embedded 7003
- EmbMilanPI-SP3 1.0.0.7not affected
AMD AMD EPYC™ Embedded 9003
- EmbGenoaPI-SP5 1.0.0.0not affected
AMD AMD Ryzen™ 6000 Series Processors with Radeon™ Graphics
- RembrandtPI-FP7 1.0.0.9bnot affected
AMD AMD Ryzen™ 7000 Series Desktop Processors
- ComboAM5 1.0.0.1not affected
AMD AMD Ryzen™ 7020 Series Processors with Radeon™ Graphics
- MendocinoPI-FT6 1.0.0.0not affected
AMD AMD Ryzen™ 7035 Series Processors with Radeon™ Graphics
- RembrandtPI-FP7 1.0.0.9bnot affected
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 7001 firmwarebefore naplespi_1.0.0.k
- amd epyc 7203 firmwarebefore milanpi_1.0.0.5
- amd epyc 7203p firmwarebefore milanpi_1.0.0.5
- amd epyc 7232p firmwarebefore romepi_1.0.0.g
- amd epyc 7251 firmwarebefore naplespi_1.0.0.k
- amd epyc 7252 firmwarebefore romepi_1.0.0.g
- amd epyc 7261 firmwarebefore naplespi_1.0.0.k
- amd epyc 7262 firmwarebefore romepi_1.0.0.g
- amd epyc 7272 firmwarebefore romepi_1.0.0.g
- amd epyc 7281 firmwarebefore naplespi_1.0.0.k
- amd epyc 7282 firmwarebefore romepi_1.0.0.g
- amd epyc 72f3 firmwarebefore milanpi_1.0.0.5
- amd epyc 7301 firmwarebefore naplespi_1.0.0.k
- amd epyc 7302 firmwarebefore romepi_1.0.0.g
- amd epyc 7302p firmwarebefore romepi_1.0.0.g
- amd epyc 7303 firmwarebefore milanpi_1.0.0.5
- amd epyc 7303p firmwarebefore milanpi_1.0.0.5
- amd epyc 7313 firmwarebefore milanpi_1.0.0.5
- amd epyc 7313p firmwarebefore milanpi_1.0.0.5
- amd epyc 7343 firmwarebefore milanpi_1.0.0.5
Same product
amd: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-20591Improper re-initialization of IOMMU during the DRTM event
may permit an untrusted platform configuration to persist, allowing an…40Plan
- CVE-2023-20584IOMMU improperly handles certain special address
ranges with invalid device table entries (DTEs), which may allow an attacker
with…24Monitor
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.
- Administrator privileges are required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-367 · Time-of-check Time-of-use (TOCTOU) Race ConditionCVSS vector
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H
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.
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.