CVE-2021-26370
HIGHCVSS 7.1/10EPSS 0.22%
Last modified
CVE-2021-26370 is a high-severity vulnerability rated 7.1/10 on the CVSS scale. Improper validation of destination address in SVC_LOAD_FW_IMAGE_BY_INSTANCE and SVC_LOAD_BINARY_BY_ATTRIB in a malicious UApp or ABL may allow an attacker to overwrite arbitrary bootloader memory with SPI ROM contents resulting in a loss of integrity and availability.. EPSS estimates a 0.22% chance of exploitation in the next 30 days.
Description
Improper validation of destination address in SVC_LOAD_FW_IMAGE_BY_INSTANCE and SVC_LOAD_BINARY_BY_ATTRIB in a malicious UApp or ABL may allow an attacker to overwrite arbitrary bootloader memory with SPI ROM contents resulting in a loss of integrity and availability.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Amd | Epyc 7763 Firmware | < milanpi-sp3_1.0.0.4 |
| Amd | Epyc 7713p Firmware | < milanpi-sp3_1.0.0.4 |
| Amd | Epyc 7713 Firmware | < milanpi-sp3_1.0.0.4 |
| Amd | Epyc 7663 Firmware | < milanpi-sp3_1.0.0.4 |
| Amd | Epyc 7643 Firmware | < milanpi-sp3_1.0.0.4 |
| Amd | Epyc 75f3 Firmware | < milanpi-sp3_1.0.0.4 |
| Amd | Epyc 7543p Firmware | < milanpi-sp3_1.0.0.4 |
| Amd | Epyc 7543 Firmware | < milanpi-sp3_1.0.0.4 |
| Amd | Epyc 7513 Firmware | < milanpi-sp3_1.0.0.4 |
| Amd | Epyc 7453 Firmware | < milanpi-sp3_1.0.0.4 |
| Amd | Epyc 74f3 Firmware | < milanpi-sp3_1.0.0.4 |
| Amd | Epyc 7443p Firmware | < milanpi-sp3_1.0.0.4 |
| Amd | Epyc 7443 Firmware | < milanpi-sp3_1.0.0.4 |
| Amd | Epyc 7413 Firmware | < milanpi-sp3_1.0.0.4 |
| Amd | Epyc 73f3 Firmware | < milanpi-sp3_1.0.0.4 |
| Amd | Epyc 7343 Firmware | < milanpi-sp3_1.0.0.4 |
| Amd | Epyc 7313p Firmware | < milanpi-sp3_1.0.0.4 |
| Amd | Epyc 7313 Firmware | < milanpi-sp3_1.0.0.4 |
| Amd | Epyc 72f3 Firmware | < milanpi-sp3_1.0.0.4 |
| Amd | Epyc 7773x Firmware | < milanpi-sp3_1.0.0.4 |
| Amd | Epyc 7473x Firmware | < milanpi-sp3_1.0.0.4 |
| Amd | Epyc 7573x Firmware | < milanpi-sp3_1.0.0.4 |
| Amd | Epyc 7373x Firmware | < milanpi-sp3_1.0.0.4 |
| Amd | Epyc 7002 Firmware | < romepi-sp3_1.0.0.c |
| Amd | Epyc 7232p Firmware | < romepi-sp3_1.0.0.c |
| Amd | Epyc 7252 Firmware | < romepi-sp3_1.0.0.c |
| Amd | Epyc 7262 Firmware | < romepi-sp3_1.0.0.c |
| Amd | Epyc 7272 Firmware | < romepi-sp3_1.0.0.c |
| Amd | Epyc 7282 Firmware | < romepi-sp3_1.0.0.c |
| Amd | Epyc 7302 Firmware | < romepi-sp3_1.0.0.c |
| Amd | Epyc 7302p Firmware | < romepi-sp3_1.0.0.c |
| Amd | Epyc 7352 Firmware | < romepi-sp3_1.0.0.c |
| Amd | Epyc 7402 Firmware | < romepi-sp3_1.0.0.c |
| Amd | Epyc 7402p Firmware | < romepi-sp3_1.0.0.c |
| Amd | Epyc 7452 Firmware | < romepi-sp3_1.0.0.c |
| Amd | Epyc 7502 Firmware | < romepi-sp3_1.0.0.c |
| Amd | Epyc 7502p Firmware | < romepi-sp3_1.0.0.c |
| Amd | Epyc 7532 Firmware | < romepi-sp3_1.0.0.c |
| Amd | Epyc 7542 Firmware | < romepi-sp3_1.0.0.c |
| Amd | Epyc 7552 Firmware | < romepi-sp3_1.0.0.c |
| Amd | Epyc 7642 Firmware | < romepi-sp3_1.0.0.c |
| Amd | Epyc 7662 Firmware | < romepi-sp3_1.0.0.c |
| Amd | Epyc 7702 Firmware | < romepi-sp3_1.0.0.c |
| Amd | Epyc 7702p Firmware | < romepi-sp3_1.0.0.c |
| Amd | Epyc 7742 Firmware | < romepi-sp3_1.0.0.c |
| Amd | Epyc 7f72 Firmware | < romepi-sp3_1.0.0.c |
| Amd | Epyc 7f52 Firmware | < romepi-sp3_1.0.0.c |
| Amd | Epyc 7f32 Firmware | < romepi-sp3_1.0.0.c |
| Amd | Epyc 7h12 Firmware | < romepi-sp3_1.0.0.c |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2021-26370?
Improper validation of destination address in SVC_LOAD_FW_IMAGE_BY_INSTANCE and SVC_LOAD_BINARY_BY_ATTRIB in a malicious UApp or ABL may allow an attacker to overwrite arbitrary bootloader memory with SPI ROM contents resulting in a loss of integrity and availability.
How severe is CVE-2021-26370?
CVE-2021-26370 has a CVSS score of 7.1/10 (HIGH severity). The EPSS model estimates a 0.22% probability of exploitation in the next 30 days.
How do I fix CVE-2021-26370?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2021
- CVE-2021-26364Insufficient bounds checking in an SMU mailbox register coul…5.5
- CVE-2021-26365Certain size values in firmware binary headers could trigger…8.2
- CVE-2021-26366An attacker, who gained elevated privileges via some other v…7.1
- CVE-2021-26367A malicious attacker in x86 can misconfigure the Trusted Mem…6
- CVE-2021-26368Insufficient check of the process type in Trusted OS (TOS) m…4.4
- CVE-2021-26369A malicious or compromised UApp or ABL may be used by an att…7.8
- CVE-2021-26371A compromised or malicious ABL or UApp could send a SHA256 s…5.5
- CVE-2021-26372Insufficient bound checks related to PCIE in the System Mana…5.5
- CVE-2021-26373Insufficient bound checks in the System Management Unit (SMU…5.5
- CVE-2021-26374Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultID…
- CVE-2021-26375Insufficient General Purpose IO (GPIO) bounds check in Syste…5.5
- CVE-2021-26376Insufficient checks in System Management Unit (SMU) FeatureC…5.5
Are you affected by CVE-2021-26370?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST