An out of bounds memory write when processing the AMD PSP1 Configuration Block (APCB) could allow an attacker with access the ability to mod
Noroxi assessment
Priority: Monitor (action score 32/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.16% (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.
- 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
An out of bounds memory write when processing the AMD PSP1 Configuration Block (APCB) could allow an attacker with access the ability to modify the BIOS image, and the ability to sign the resulting image, to potentially modify the APCB block resulting in arbitrary code execution.
- Published
- Aug 13, 2024
- Updated
- Jun 16, 2026
- EPSS
- 0.1% · 4th percentile
- CWE
- CWE-787
Report tools
Action score
32
Monitor
Low priority for now.
- CVSS
- 32 / 40 · 8.2 / 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
- 8.2
- CNA · AMD
- 7.2
- 1.0 point gap
CVSS:3.1/AV:L/AC:H/PR:H/UI:R/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.
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 126 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- amd epyc 7001 firmwareall versions
- 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.c
- amd epyc 7251 firmwareall versions
- amd epyc 7252 firmwarebefore romepi_1.0.0.c
- amd epyc 7261 firmwareall versions
- amd epyc 7262 firmwarebefore romepi_1.0.0.c
- amd epyc 7272 firmwarebefore romepi_1.0.0.c
- amd epyc 7281 firmwareall versions
- amd epyc 7282 firmwarebefore romepi_1.0.0.c
- amd epyc 72f3 firmwarebefore milanpi_1.0.0.5
- amd epyc 7301 firmwareall versions
- amd epyc 7302 firmwarebefore romepi_1.0.0.c
- amd epyc 7302p firmwarebefore romepi_1.0.0.c
- 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
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 Athlon™ 3000 Series Desktop Processors with Radeon™ Graphics
- variousaffected
AMD AMD Athlon™ 3000 Series Mobile Processors with Radeon™ Graphics
- various, variousaffected
AMD AMD EPYC™ 7001 Series Processors
- variousaffected
AMD AMD EPYC™ 7002 Series Processors
- RomePI 1.0.0.Cnot affected
AMD AMD EPYC™ 7003 Series Processors
- MilanPI 1.0.0.5not affected
AMD AMD EPYC™ Embedded 3000 Series Processors
- Variousaffected
AMD AMD EPYC™ Embedded 7002 Series Processors
- EmbRomePI-SP3 1.0.0.6not affected
AMD AMD EPYC™ Embedded 7003 Series Processors
- EmbMilanPI-SP3 1.0.0.2not affected
AMD AMD Ryzen™ 3000 Series Desktop Processors
- variousaffected
AMD AMD Ryzen™ 3000 Series Mobile Processors with Radeon™ Graphics
- variousaffected
AMD AMD Ryzen™ 3000 Series Processors with Radeon™ Graphics
- CezannePI-FP6 1.0.0.Enot affected
AMD AMD Ryzen™ 4000 Series Desktop Processors with Radeon™ Graphics
- variousaffected
Same product
amd: all recordsOther highest-scoring records for the same primary product.
- 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
- CVE-2023-31355Improper restriction of write operations in SNP firmware could allow a malicious hypervisor to overwrite a guest's UMC seed potentially allo24Monitor
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.
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.
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
- 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
- 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
- Local
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-787 · Out-of-bounds WriteCVSS vector
CVSS:3.1/AV:L/AC:L/PR:H/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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
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.