Improper restriction of write operations in SNP firmware could allow a malicious hypervisor to overwrite a guest's UMC seed potentially allo
Noroxi assessment
Priority: Monitor (action score 24/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.44% (FIRST EPSS).
- Someone with local access to the system can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: AMD 3rd Gen AMD EPYC™ Processors MilanPI 1.0.0.D; AMD 4th Gen AMD EPYC™ Processors GenoaPI 1.0.0.C; AMD AMD EPYC™ Embedded 7003 EmbMilanPI-SP3 1.0.0.9.
Low priority for now. Upgrade to AMD 3rd Gen AMD EPYC™ Processors MilanPI 1.0.0.D; AMD 4th Gen AMD EPYC™ Processors GenoaPI 1.0.0.C; AMD AMD EPYC™ Embedded 7003 EmbMilanPI-SP3 1.0.0.9 or later.
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 restriction of write operations in SNP firmware could allow a malicious hypervisor to overwrite a guest's UMC seed potentially allowing reading of memory from a decommissioned guest.
- Published
- Aug 5, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.4% · 37th percentile
- CWE
- CWE-119
Report tools
Action score
24
Monitor
Low priority for now.
- CVSS
- 24 / 40 · 6.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 6.0
- CNA · AMD
- 6.0
- agree
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
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
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 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 7203 firmware | cpe:2.3:o:amd:epyc_7203_firmware |
| amd | epyc 7203 | cpe:2.3:h:amd:epyc_7203 |
| amd | epyc 7203p firmware | cpe:2.3:o:amd:epyc_7203p_firmware |
| amd | epyc 7203p | cpe:2.3:h:amd:epyc_7203p |
| amd | epyc 72f3 firmware | cpe:2.3:o:amd:epyc_72f3_firmware |
| amd | epyc 72f3 | cpe:2.3:h:amd:epyc_72f3 |
| amd | epyc 7303 firmware | cpe:2.3:o:amd:epyc_7303_firmware |
| amd | epyc 7303 | cpe:2.3:h:amd:epyc_7303 |
| amd | epyc 7303p firmware | cpe:2.3:o:amd:epyc_7303p_firmware |
| amd | epyc 7303p | cpe:2.3:h:amd:epyc_7303p |
| amd | epyc 7313 firmware | cpe:2.3:o:amd:epyc_7313_firmware |
| amd | epyc 7313 | cpe:2.3:h:amd:epyc_7313 |
and 160 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.d
- amd epyc 7203p firmwarebefore milanpi_1.0.0.d
- amd epyc 72f3 firmwarebefore milanpi_1.0.0.d
- amd epyc 7303 firmwarebefore milanpi_1.0.0.d
- amd epyc 7303p firmwarebefore milanpi_1.0.0.d
- amd epyc 7313 firmwarebefore milanpi_1.0.0.d
- amd epyc 7313p firmwarebefore milanpi_1.0.0.d
- amd epyc 7343 firmwarebefore milanpi_1.0.0.d
- amd epyc 7373x firmwarebefore milanpi_1.0.0.d
- amd epyc 73f3 firmwarebefore milanpi_1.0.0.d
- amd epyc 7413 firmwarebefore milanpi_1.0.0.d
- amd epyc 7443 firmwarebefore milanpi_1.0.0.d
- amd epyc 7443p firmwarebefore milanpi_1.0.0.d
- amd epyc 7453 firmwarebefore milanpi_1.0.0.d
- amd epyc 7473x firmwarebefore milanpi_1.0.0.d
- amd epyc 74f3 firmwarebefore milanpi_1.0.0.d
- amd epyc 7513 firmwarebefore milanpi_1.0.0.d
- amd epyc 7543 firmwarebefore milanpi_1.0.0.d
- amd epyc 7543p firmwarebefore milanpi_1.0.0.d
- amd epyc 7573x firmwarebefore milanpi_1.0.0.d
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 3rd Gen AMD EPYC™ Processors
- various and later · before MilanPI 1.0.0.Daffected · Platform Initialization
AMD 4th Gen AMD EPYC™ Processors
- various and later · before GenoaPI 1.0.0.Caffected · Platform Initialization
AMD AMD EPYC™ Embedded 7003
- various and later · before EmbMilanPI-SP3 1.0.0.9affected · Platform Initialization
AMD AMD EPYC™ Embedded 9003
- various and later · before EmbGenoaPI-SP5 1.0.0.7affected · Platform Initialization
Same product
amd: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-26344An out of bounds memory write when processing the AMD
PSP1 Configuration Block (APCB) could allow an attacker with access the ability
to mod32Monitor
- CVE-2024-21980Improper restriction of write operations in SNP firmware could allow a malicious hypervisor to potentially overwrite a guest's memory or UMC31Monitor
- CVE-2024-21978Improper input validation in SEV-SNP could allow a malicious hypervisor to read or overwrite guest memory potentially leading to data leakag31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| AMD 3rd Gen AMD EPYC™ Processors | MilanPI 1.0.0.D | Vendor (CNA) |
| AMD 4th Gen AMD EPYC™ Processors | GenoaPI 1.0.0.C | Vendor (CNA) |
| AMD AMD EPYC™ Embedded 7003 | EmbMilanPI-SP3 1.0.0.9 | Vendor (CNA) |
| AMD AMD EPYC™ Embedded 9003 | EmbGenoaPI-SP5 1.0.0.7 | Vendor (CNA) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:8 | 2023-12-08 |
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.
- First PoC-242 d
- Published
- TodayOct 23, 2026+809 d
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 researchersFinders, 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.
- CVE-2024-219800 days apartImproper restriction of write operations in SNP firmware could allow a malicious hypervisor to potentially overwrite a guest's memory or UMC31Monitor
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
- Someone with local access to the system can trigger it.
- Administrator privileges are required.
- 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
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-119 · Improper Restriction of Operations within the Bounds of a Memory BufferCVSS vector
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/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.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Overflow BuffersCAPEC-100likelihood: High · Very High
- Buffer ManipulationCAPEC-123likelihood: High · Very High
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
- Filter Failure through Buffer OverflowCAPEC-24likelihood: High · High
- MIME ConversionCAPEC-42likelihood: High · High
- Overflow Binary Resource FileCAPEC-44likelihood: High · Very High
- Buffer Overflow via Symbolic LinksCAPEC-45likelihood: High · High
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.