Evidence used
- No CISA KEV confirmation is currently recorded.
- Exploitation requires an existing local or physical foothold with privileges.
- EPSS is 0.10% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2024
CVE-2023-20518High confidence
AMD AMD EPYC™ 9004 Series Processors — Incomplete Cleanup
AMD · AMD EPYC™ 9004 Series Processors
1.9LowCVSS 3.1
Scheduled
Patch availableLow technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityLow→Operational priority:Low, unchanged from published severity.unchanged
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict local access and enforce least privilege on affected hosts.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs AMD AMD EPYC™ 9004 Series Processors and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Low technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
Patch available01
What, why and how
Incomplete cleanup in the ASP may expose the Master Encryption Key (MEK) to a privileged attacker with access to the BIOS menu or UEFI shell and a memory exfiltration vulnerability, potentially resulting in loss of confidentiality.
What
Incomplete cleanup in the ASP may expose the Master Encryption Key (MEK) to a privileged attacker with access to the BIOS menu or UEFI shell and a memory exfiltration vulnerability, potentially resulting in loss of confidentiality.
Why
The product does not properly clean up and remove temporary or supporting resources after they have been used.
How
An attacker operating through local access may attempt exploitation with elevated privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
Incomplete cleanup in the ASP may expose the Master Encryption Key (MEK) to a privileged attacker with access to the BIOS menu or UEFI shell and a memory exfiltration vulnerability, potentially resulting in loss of confidentiality.
Why
The product does not properly clean up and remove temporary or supporting resources after they have been used.
How
An attacker operating through local access may attempt exploitation with elevated privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- local access → Incomplete Cleanup → cause the confidentiality, integrity or availability impact described by the vendor
- Attack surface
- Local
- Privileges required
- High: elevated access is required
- User interaction
- None
- Attack complexity
- High: exploitation depends on specific conditions
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-459 ↗
CWE-459: Incomplete Cleanup. The product does not properly clean up and remove temporary or supporting resources after they have been used.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:N/A:NCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRHighPrivileges required: The attacker needs elevated or administrative privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CLowConfidentiality impact: A successful attack can cause a limited loss.INoneIntegrity impact: No direct loss is represented by this metric.ANoneAvailability impact: No direct loss is represented by this metric.- Post-exploitation / living off the land
- The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Patch available
- Fixed
- AMD EPYC™ 9004 Series Processors: GenoaPI 1.0.0.4
- AMD Ryzen™ 3000 Series Desktop Processors: ComboAM4V1 1.0.0.A, ComboAM4V2 1.2.0.A
- AMD Ryzen™ 5000 Series Desktop Processors: ComboAM4V2 1.2.0.A
- AMD Ryzen™ 5000 Series Desktop Processor with Radeon™ Graphics: ComboAM4V2 1.2.0.A
- AMD Ryzen™ 7000 Series Desktop Processors: ComboAM5 1.0.0.6
- AMD Athlon™ 3000 Series Desktop Processors with Radeon™ Graphics: ComboAM4V2 1.2.0.A, ComboAM4V1 1.0.0.A
- AMD Ryzen™ 4000 Series Desktop Processors with Radeon™ Graphics: ComboAM4V2 1.2.0.A
- AMD Ryzen™ Threadripper™ 3000 Series Processors: CastlePeakPI-SP3r3 1.0.0.9
- AMD Ryzen™ Threadripper™ PRO 3000WX Series Processors: ChagallWSPI-sWRX8 1.0.0.6, CastlePeakWSPI-sWRX8 1.0.0.B
- AMD Ryzen™ Threadripper™ PRO 5000WX Processors: ChagallWSPI-sWRX8 1.0.0.6
- AMD Athlon™ 3000 Series Mobile Processors with Radeon™ Graphics: PicassoPI-FP5 1.0.0.F, PollockPI-FT5 1.0.0.5
- AMD Ryzen™ 3000 Series Mobile Processor with Radeon™ Graphics: PicassoPI-FP5 1.0.0.F
- AMD Ryzen™ 4000 Series Mobile Processors with Radeon™ Graphics: RenoirPI-FP6 1.0.0.C
- AMD Ryzen™ 5000 Series Mobile Processors with Radeon™ Graphics: CezannePI-FP6 1.0.0.E, CezannePI-FP6 1.0.0.E
- AMD Ryzen™ 7020 Series Processors with Radeon™ Graphics: MendocinoPI-FT6 1.0.0.4
- AMD Ryzen™ 6000 Series Processors with Radeon™ Graphics: RembrandtPI-FP7 1.0.0.8
- AMD Ryzen™ 7035 Series Processors with Radeon™ Graphics: RembrandtPI-FP7 1.0.0.8
- AMD Ryzen™ 5000 Series Processors with Radeon™ Graphics: CezannePI-FP6 1.0.0.E
- AMD Ryzen™ 3000 Series Processors with Radeon™ Graphics: CezannePI-FP6 1.0.0.E
- AMD Ryzen™ Embedded R1000 Series Processors: EmbeddedPI-FP5 1.2.0.A
- AMD Ryzen™ Embedded R2000 Series Processors: EmbeddedR2KPI-FP5 1.0.0.2
- AMD Ryzen™ Embedded 5000 Series Processors: EmbAM4PI 1.0.0.3
- AMD Ryzen™ Embedded 7000 Series Processors: EmbeddedAM5PI 1.0.0.0
- AMD Ryzen™ Embedded V2000 Series Processors: EmbeddedPI-FP6 1.0.0.8
- AMD Ryzen™ Embedded V3000 Series Processors: EmbeddedPI-FP7r2 1.0.0.5
- Action
- Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
- Workaround
- No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04
Evidence and provenance
Published 13 Aug 2024 · Last source change 5 Nov 2024, 17:10 UTC · CWE-459 · Incomplete Cleanup
CVE recordCVE.org · 5.1
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2023-24697
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceCISA ADP
NVD statusNVD not scheduled
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.
CVE published
Fixed release or patch reference recorded
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.