CVE-2021-26402: Insufficient bounds checking in ASP (AMD Secure Processor) firmware while handling BIOS mailbox commands, may allow an attacker to write…
Noroxi assessment
Priority: Monitor (action score 28/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.18% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. 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
Insufficient bounds checking in ASP (AMD Secure Processor) firmware while handling BIOS mailbox commands, may allow an attacker to write partially-controlled data out-of-bounds to SMM or SEV-ES regions which may lead to a potential loss of integrity and availability.
- Published
- Jan 11, 2023
- Updated
- Jun 16, 2026
- EPSS
- 0.1% · 8th percentile
- CWE
- CWE-787
Report tools
Action score
28
Low priority for now.
- CVSS
- 28 / 40 · 7.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
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.
Is your version affected? Check itNoroxi 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 7003 firmware | cpe:2.3:o:amd:epyc_7003_firmware |
| amd | epyc 7003 | cpe:2.3:h:amd:epyc_7003 |
| amd | epyc 72f3 firmware | cpe:2.3:o:amd:epyc_72f3_firmware |
| amd | epyc 72f3 | cpe:2.3:h:amd:epyc_72f3 |
| amd | epyc 7313 firmware | cpe:2.3:o:amd:epyc_7313_firmware |
| amd | epyc 7313 | cpe:2.3:h:amd:epyc_7313 |
| amd | epyc 7h12 firmware | cpe:2.3:o:amd:epyc_7h12_firmware |
| amd | epyc 7h12 | cpe:2.3:h:amd:epyc_7h12 |
| amd | epyc 7f72 firmware | cpe:2.3:o:amd:epyc_7f72_firmware |
| amd | epyc 7f72 | cpe:2.3:h:amd:epyc_7f72 |
| amd | epyc 7f52 firmware | cpe:2.3:o:amd:epyc_7f52_firmware |
| amd | epyc 7f52 | cpe:2.3:h:amd:epyc_7f52 |
and 88 more
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 2nd Gen EPYC
- Variousaffected
AMD 3rd Gen EPYC
- variousaffected
Affected versions · NVD (20)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- amd epyc 7002 firmwarebefore romepi_1.0.0.c
- amd epyc 7003 firmwarebefore milanpi_1.0.0.4
- amd epyc 7232p firmwarebefore romepi_1.0.0.c
- amd epyc 7252 firmwarebefore romepi_1.0.0.c
- amd epyc 7262 firmwarebefore romepi_1.0.0.c
- amd epyc 7272 firmwarebefore romepi_1.0.0.c
- amd epyc 7282 firmwarebefore romepi_1.0.0.c
- amd epyc 72f3 firmwarebefore milanpi_1.0.0.4
- amd epyc 7302 firmwarebefore romepi_1.0.0.c
- amd epyc 7302p firmwarebefore romepi_1.0.0.c
- amd epyc 7313 firmwarebefore milanpi_1.0.0.4
- amd epyc 7313p firmwarebefore milanpi_1.0.0.4
- amd epyc 7343 firmwarebefore milanpi_1.0.0.4
- amd epyc 7352 firmwarebefore romepi_1.0.0.c
- amd epyc 7373x firmwarebefore milanpi_1.0.0.4
- amd epyc 73f3 firmwarebefore milanpi_1.0.0.4
- amd epyc 7402 firmwarebefore romepi_1.0.0.c
- amd epyc 7402p firmwarebefore romepi_1.0.0.c
- amd epyc 7413 firmwarebefore milanpi_1.0.0.4
- amd epyc 7443 firmwarebefore milanpi_1.0.0.4
Same product
amd: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-26398Insufficient input validation in SYS_KEY_DERIVE system call in a compromised user application or ABL may allow an attacker to corrupt ASP…31Monitor
- CVE-2021-26316Failure to validate the communication buffer and communication service in the BIOS may allow an attacker to tamper with the buffer…31Monitor
- CVE-2023-20531Insufficient bound checks in the SMU may allow an attacker to update the SRAM from/to address space to an invalid value potentially…30Monitor
Published before and after this one in the same product
- Later →CVE-2023-20523Jan 11, 2023 · TOCTOU in the ASP may allow a physical attacker to write beyond the buffer bounds, potentially leading to a loss of integrity or denial of…22Monitor
- Later →CVE-2023-20525Jan 11, 2023 · Insufficient syscall input validation in the ASP Bootloader may allow a privileged attacker to read memory outside the bounds of a mapped…26Monitor
- Later →CVE-2023-20527Jan 11, 2023 · Improper syscall input validation in the ASP Bootloader may allow a privileged attacker to read memory out-of-bounds, potentially leading…26Monitor
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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-787 · Out-of-bounds WriteCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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 (0)
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.