Supermicro is aware of potential vulnerabilities affecting AMD Secure Encrypted Virtualization (SEV) on AMD EPYC™ and AMD EPYC™ Embedded processor platforms were identified through internal research. AMD has provided mitigations to address these issues. This vulnerability affects BIOS in Supermicro H12, H13 and H14 products.
| CVE ID | CVE Description | CVSS Score |
|---|---|---|
| Improper access control in AMD Secure Encrypted Virtualization (SEV) firmware could allow a malicious hypervisor to bypass Reverse Map Table (RMP) protections, potentially impacting the integrity of Secure Encrypted Virtualization-Secure Nested Paging (SEV-SNP) guest memory. | 5.9 CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:N/SC:N/SI:H/SA:N |
| Unverified ownership in Secure Encrypted Virtualization (SEV) firmware could allow a privileged attacker with access to a malicious hypervisor to overwrite guest memory if segmented Reverse Map Table (RMP) is enabled potentially resulting in loss of guest data integrity. | 5.9 CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:N/SC:N/SI:H/SA:N |
| Improper resource reuse in the AMD Secure Encrypted Virtualization (SEV) firmware could allow an attacker with hypervisor access to write to the Reverse Map Table (RMP) protected memory, potentially resulting in loss of guest memory integrity. | 5.9 CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:N/SC:N/SI:H/SA:N |
| Improper handling of overlap between protected memory ranges in the Secure Encrypted Virtualization (SEV) firmware could allow a privileged attacker to cause misconfigurations in the RMP potentially resulting in loss of integrity. | 5.9 CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:N/SC:N/SI:H/SA:N |
| Insufficient Granularity of Access Control in AMD Secure Encrypted Virtualization (SEV) firmware could allow an attacker with administrative privileges attacker to write to a trusted region used by AMD Secure Encrypted Virtualization-Encrypted State (SEV-ES), potentially resulting in loss of integrity. | CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:N/SC:N/SI:H/SA:N |
| Improper validation of unsafe equivalence in input could allow an attacker with high privileges to reclaim the ring buffer queue status page, potentially resulting in loss of guest memory integrity. | 5.9 CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:N/SC:N/SI:H/SA:N |
| Expected behavior violation in AMD Secure Encrypted Virtualization (SEV) firmware could allow a malicious hypervisor to bypass Reverse Map Table (RMP) protections, potentially resulting in a loss of Secure Encrypted Virtualization-Secure Nested Paging (SEV-SNP) guest memory integrity. | 5.9 CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:N/SC:N/SI:H/SA:N |
| Improper access control within the AMD Secure Encrypted Virtualization (SEV) firmware could allow an attacker with administrative privileges to tamper with memory, potentially resulting in loss of guest memory integrity. | 4.0 CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:N/VC:N/VI:N/VA:N/SC:N/SI:H/SA:N |
| A time-of-check to time-of-use (TOCTOU) race condition in the AMD SEV Secure Encrypted Virtualization (SEV) firmware could allow an attacker with administrative privileges to bypass security checks on scatter lists, potentially resulting in loss of guest integrity. | 4.0 CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:N/VC:N/VI:N/VA:N/SC:N/SI:H/SA:N |
| Improper validation of Reverse Map Table (RMP) entries in the Secure Encrypted Virtualization (SEV) firmware could allow a privileged attacker to trigger concurrent modifications to RMP entries without proper synchronization potentially resulting in loss of data integrity. | 4.0 CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:N/VC:N/VI:N/VA:N/SC:N/SI:H/SA:N |
Affected products:
Supermicro BIOS on server H11, H12, H13 and H14 motherboards.
| AMD Motherboard Generation | BIOS version with the fix |
|---|---|
| H12 – H12SSW-AN6 – EPYC™ 7002/7003 series | v 3.7 |
| H12 – H12SSW-iNR/NTR – EPYC 7002/7003 series | v 3.7 |
| H12 – H12SSW-iNL/NTL – EPYC 7002/7003 series | v 3.7 |
| H12 – H12DSG-O-CPU – EPYC 7002/7003 series | v 3.7 |
| H12 – H12DST-B – EPYC 7002/7003 series | v 3.7 |
| H12 – H12SST-PS – EPYC 7002/7003 series | v 3.7 |
| H12 – H12SSW-iN/NT – EPYC 7002/7003 series | v 3.8 |
| H12 – BH12SSi-M25 – EPYC 7002/7003 series | v 3.7 |
| H12 – H12DSU-iN – EPYC 7002/7003 series | v 3.7 |
| H12 – H12SSFF-AN6 – EPYC 7002/7003 series | v 3.7 |
| H12 – H12SSL-i/C/CT/NT – EPYC 7002/7003 series | v 3.7 |
| H12 – H12DSi-N6/NT6 – EPYC 7002/7003 series | v 3.7 |
| H12 – H12SSFR-AN6 – EPYC 7002/7003 series | v 3.7 |
| H12 – H12DSG-Q-CPU6 – EPYC 7002/7003 series | v 3.7 |
| H12 – H12SSG-AN6 – EPYC 7002/7003 series | v 3.7 |
| H12 – H12DGQ-NT6 – EPYC 7002/7003 series | v 3.7 |
| H12 – H12SSG-ANP6 – EPYC 7002/7003 series | v 3.7 |
| H12 – H12DGO-6 – EPYC 7002/7003 series | v 3.7 |
| H12 – H12DSU-iNR – EPYC 7002/7003 series | v 3.7 |
| H13 – H13SVW-N/NT – EPYC 8004/8005 series | v 2.2 |
| H13 – H13SSW – EPYC 9004/9005 series | v 4.1 |
| H13 – H13DSH – EPYC 9004/9005 series | v 4.0 |
| H13 – H13DSG-O-CPU – EPYC 9004/9005 series | v 4.1 |
| H13 – H13SST-G/GC – EPYC 9004/9005 series | v 3.8 |
| H13 – H13SSL-N/NT – EPYC 9004/9005 series | v 4.1 |
| H13 – H13SSH – EPYC 9004/9005 series | v 4.1a |
| H13 – H13SSH-E – EPYC 9004/9005 series | v 4.2 |
| H13 – H13DSG-O-CPU-D – EPYC 9004 series | v 4.0 |
| H13 – H13SSF – EPYC 9004/9005 series | v 4.1 |
| H13 – H13DSG-OM – EPYC 9004/9005 series | v 4.1 |
| H14 – H14DSH – EPYC 9004/9005 series | v 2.0 |
| H14 – H14SST-G – EPYC 9004/9005 series | v 2.0 |
| H14 – H14SST-GE – EPYC 9005 series | v 2.0 |
| H14 – H14DSG-OD – EPYC 9004/9005 series | v 2.1 |
| H14 – H14SHM – EPYC 9004/9005 series | v 2.1 |
| H14 – H14DST-F/FL – EPYC 9005 series | v 2.0 |
| H14 – H14DSG-O-CPU – EPYC 9004/9005 series | v 2.2 |
| H14 – H14SSL-N/NT – EPYC 9004/9005 series | v 2.1 |
| H14 – H14DSG-OM – EPYC 9004/9005 series | v 1.5 |
| H14 – H14SSF – EPYC 9005 series | v 1.0 |
Remediation:
All affected Supermicro motherboard SKUs will require a BMC update to mitigate these potential vulnerabilities.
Updated BMC firmware has been created to mitigate these potential vulnerabilities. Supermicro is currently testing and validating affected products. Please check Release notes for the resolution.