CVE-2021-46754

9.1 CRITICAL

📋 TL;DR

This vulnerability in AMD's Secure Processor bootloader allows attackers with compromised Uapp or ABL components to force the bootloader to leak sensitive information to the System Management Unit. This could lead to loss of confidentiality and integrity of secure data. Affected systems include AMD processors with vulnerable ASP firmware.

💻 Affected Systems

Products:
  • AMD processors with ASP (AMD Secure Processor)
Versions: Specific firmware versions as detailed in AMD advisories
Operating Systems: All operating systems running on affected AMD hardware
Default Config Vulnerable: ⚠️ Yes
Notes: Requires compromised Uapp or ABL components to exploit. Affects systems with vulnerable ASP firmware versions.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete compromise of secure processor environment, exposure of cryptographic keys and secure data, potential for persistent firmware-level attacks.

🟠

Likely Case

Information disclosure from secure processor to less privileged components, enabling further attacks on system security.

🟢

If Mitigated

Limited impact with proper firmware updates and secure boot enabled.

🌐 Internet-Facing: LOW - Requires local access or compromised firmware components.
🏢 Internal Only: HIGH - Attackers with physical access or compromised firmware can exploit this vulnerability.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: HIGH

Requires compromised Uapp or ABL components, making exploitation complex. No public exploits known at this time.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Refer to AMD security bulletins for specific firmware versions

Vendor Advisory: https://www.amd.com/en/corporate/product-security/bulletin/AMD-SB-4001

Restart Required: Yes

Instructions:

1. Check AMD security bulletins for affected products. 2. Obtain updated firmware from system/motherboard manufacturer. 3. Apply firmware update following manufacturer instructions. 4. Reboot system to activate new firmware.

🔧 Temporary Workarounds

Enable Secure Boot

all

Enable Secure Boot in BIOS/UEFI settings to help prevent unauthorized firmware modifications

Physical Security Controls

all

Implement strict physical access controls to prevent local attacks

🧯 If You Can't Patch

  • Isolate affected systems from untrusted networks and users
  • Implement strict physical security controls and monitor for unauthorized access

🔍 How to Verify

Check if Vulnerable:

Check system firmware version against AMD security bulletins. Use manufacturer tools to verify ASP firmware version.

Check Version:

Manufacturer-specific commands vary. Check BIOS/UEFI settings or use manufacturer firmware update tools.

Verify Fix Applied:

Verify firmware version has been updated to patched version using system BIOS/UEFI interface or manufacturer tools.

📡 Detection & Monitoring

Log Indicators:

  • Unexpected firmware update attempts
  • BIOS/UEFI configuration changes
  • Secure boot violations

Network Indicators:

  • Unusual outbound traffic from management interfaces

SIEM Query:

Search for firmware update events, secure boot violations, or unauthorized BIOS/UEFI access attempts

🔗 References

📤 Share & Export