cve.bz

CVE-2023-20591 amd: Improper Initialization

10.0 criticalEPSS 0.3%

Critical (10.0) in amd. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
Improper re-initialization of IOMMU during the DRTM event may permit an untrusted platform configuration to persist, allowing an attacker to read or modify hypervisor memory, potentially resulting in loss of confidentiality, integrity, and availability.

Severity

CVSS 3.1

10.0 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 23rd percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2024-08-14. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-665 Improper Initialization
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2023-20591 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-20591?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-20591?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2023-20591 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
amd:epyc_8024pn_firmwarebefore genoapi_1.0.0.8
amd:epyc_8024p_firmwarebefore genoapi_1.0.0.8
amd:epyc_8124pn_firmwarebefore genoapi_1.0.0.8
amd:epyc_8124p_firmwarebefore genoapi_1.0.0.8
amd:epyc_8224pn_firmwarebefore genoapi_1.0.0.8
amd:epyc_8224p_firmwarebefore genoapi_1.0.0.8
amd:epyc_8324pn_firmwarebefore genoapi_1.0.0.8
amd:epyc_8324p_firmwarebefore genoapi_1.0.0.8
amd:epyc_8434pn_firmwarebefore genoapi_1.0.0.8
amd:epyc_8434p_firmwarebefore genoapi_1.0.0.8
amd:epyc_8534pn_firmwarebefore genoapi_1.0.0.8
amd:epyc_8534p_firmwarebefore genoapi_1.0.0.8
amd:epyc_9734_firmwarebefore genoapi_1.0.0.8
amd:epyc_9754s_firmwarebefore genoapi_1.0.0.8
amd:epyc_9754_firmwarebefore genoapi_1.0.0.8
amd:epyc_9184x_firmwarebefore genoapi_1.0.0.8
amd:epyc_9384x_firmwarebefore genoapi_1.0.0.8
amd:epyc_9684x_firmwarebefore genoapi_1.0.0.8
amd:epyc_9124_firmwarebefore genoapi_1.0.0.8
amd:epyc_9174f_firmwarebefore genoapi_1.0.0.8
amd:epyc_9224_firmwarebefore genoapi_1.0.0.8
amd:epyc_9254_firmwarebefore genoapi_1.0.0.8
amd:epyc_9274f_firmwarebefore genoapi_1.0.0.8
amd:epyc_9334_firmwarebefore genoapi_1.0.0.8
amd:epyc_9354_firmwarebefore genoapi_1.0.0.8
amd:epyc_9354p_firmwarebefore genoapi_1.0.0.8
amd:epyc_9374f_firmwarebefore genoapi_1.0.0.8
amd:epyc_9454_firmwarebefore genoapi_1.0.0.8
amd:epyc_9454p_firmwarebefore genoapi_1.0.0.8
amd:epyc_9474f_firmwarebefore genoapi_1.0.0.8
amd:epyc_9534_firmwarebefore genoapi_1.0.0.8
amd:epyc_9554_firmwarebefore genoapi_1.0.0.8
amd:epyc_9554p_firmwarebefore genoapi_1.0.0.8
amd:epyc_9634_firmwarebefore genoapi_1.0.0.8
amd:epyc_9654_firmwarebefore genoapi_1.0.0.8
amd:epyc_9654p_firmwarebefore genoapi_1.0.0.8
amd:epyc_7203_firmwarebefore milanpi_1.0.0.b
amd:epyc_7203p_firmwarebefore milanpi_1.0.0.b
amd:epyc_72f3_firmwarebefore milanpi_1.0.0.b
amd:epyc_7303_firmwarebefore milanpi_1.0.0.b
amd:epyc_7303p_firmwarebefore milanpi_1.0.0.b
amd:epyc_7313_firmwarebefore milanpi_1.0.0.b
amd:epyc_7313p_firmwarebefore milanpi_1.0.0.b
amd:epyc_7343_firmwarebefore milanpi_1.0.0.b
amd:epyc_73f3_firmwarebefore milanpi_1.0.0.b
amd:epyc_7373x_firmwarebefore milanpi_1.0.0.b
amd:epyc_7413_firmwarebefore milanpi_1.0.0.b
amd:epyc_7443_firmwarebefore milanpi_1.0.0.b
amd:epyc_7443p_firmwarebefore milanpi_1.0.0.b
amd:epyc_74f3_firmwarebefore milanpi_1.0.0.b
amd:epyc_7453_firmwarebefore milanpi_1.0.0.b
amd:epyc_7473x_firmwarebefore milanpi_1.0.0.b
amd:epyc_7513_firmwarebefore milanpi_1.0.0.b
amd:epyc_7543_firmwarebefore milanpi_1.0.0.b
amd:epyc_7543p_firmwarebefore milanpi_1.0.0.b
amd:epyc_75f3_firmwarebefore milanpi_1.0.0.b
amd:epyc_7573x_firmwarebefore milanpi_1.0.0.b
amd:epyc_7643_firmwarebefore milanpi_1.0.0.b
amd:epyc_7773x_firmwarebefore milanpi_1.0.0.b
amd:epyc_7643p_firmwarebefore milanpi_1.0.0.b
amd:epyc_7663_firmwarebefore milanpi_1.0.0.b
amd:epyc_7663p_firmwarebefore milanpi_1.0.0.b
amd:epyc_7713_firmwarebefore milanpi_1.0.0.b
amd:epyc_7713p_firmwarebefore milanpi_1.0.0.b
amd:epyc_7763_firmwarebefore milanpi_1.0.0.b

Attack patterns (CAPEC)

  • CAPEC-26 Leveraging Race Conditions Likelihood: High · Severity: High
  • CAPEC-29 Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON