Skip to content
Noroxi
NVD / CVE Program· CNA AMD

CVE-2023-20591: Improper re-initialization of IOMMU during the DRTM event may permit an untrusted platform configuration to persist, allowing an attacker to

Noroxi assessment

Priority: Plan (action score 40/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.29% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • According to the record, no fixed version is available yet.
  • Severity is disputed: the assigning authority (CNA) scores it 6.5, NVD 10.0.

Add it to your regular patch cycle. 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

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.

CriticalCVSS 10.0 · v3.1—No exploit No fix recorded
Published
Aug 13, 2024
Updated
Jun 17, 2026
EPSS
0.2% · 22th percentile

Report tools

JSON

Action score

40

Plan

Add it to your regular patch cycle.

CVSS
40 / 40 · 10.0 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
10.0
CNA · AMD
6.5
3.5 point gap

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:L

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.

Follow CVE-2023-20591

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for amd records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi 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 help

Affected 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.

VendorProduct
amdepyc 8024pn firmware
amdepyc 8024pn
amdepyc 8024p firmware
amdepyc 8024p
amdepyc 8124pn firmware
amdepyc 8124pn
amdepyc 8124p firmware
amdepyc 8124p
amdepyc 8224pn firmware
amdepyc 8224pn
amdepyc 8224p firmware
amdepyc 8224p

and 118 more

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • 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 7373x firmwarebefore milanpi_1.0.0.b
  • amd epyc 73f3 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 7453 firmwarebefore milanpi_1.0.0.b
  • amd epyc 7473x firmwarebefore milanpi_1.0.0.b
  • amd epyc 74f3 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 7573x firmwarebefore milanpi_1.0.0.b

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™ 7003 Series Processors

    • MilanPI 1.0.0.Bnot affected

  • AMD AMD EPYC™ 9004 Series Processors

    • Genoa 1.0.0.8not affected

  • AMD AMD EPYC™ Embedded 7003 Series Processors

    • EmbMilanPI-SP3 1.0.0.7not affected

  • AMD AMD EPYC™ Embedded 9003 Series Processors

    • EmbGenoaPI-SP5 1.0.0.3not affected

Same product

amd: all records

Other highest-scoring records for the same primary product.

  • CVE-2023-20578A 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
    25Monitor
  • CVE-2023-20584IOMMU improperly handles certain special address ranges with invalid device table entries (DTEs), which may allow an attacker with privilege
    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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted

Impact can extend beyond the vulnerable component (scope changes).

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Changed
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-665 · Improper Initialization

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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.

ATT&CK techniques

—

Change log

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.

All records