CVE-2024-55567

7.5 HIGH

📋 TL;DR

This vulnerability allows attackers to write arbitrary memory inside SMRAM and execute arbitrary code at SMM level due to improper input validation in UsbCoreDxe. It affects systems running Insyde InsydeH2O kernel versions 5.4 before 05.47.01, 5.5 before 05.55.01, 5.6 before 05.62.01, and 5.7 before 05.71.01. This is a System Management Mode vulnerability that gives attackers high-privilege access.

💻 Affected Systems

Products:
  • Insyde InsydeH2O kernel
Versions: 5.4 before 05.47.01, 5.5 before 05.55.01, 5.6 before 05.62.01, 5.7 before 05.71.01
Operating Systems: Any OS running on affected InsydeH2O firmware
Default Config Vulnerable: ⚠️ Yes
Notes: Affects systems with InsydeH2O UEFI firmware. The vulnerability is in the SMM module, so it affects the system regardless of the installed operating system.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete system compromise with SMM-level code execution, allowing attackers to bypass all security controls, install persistent firmware-level malware, and gain full control over the system.

🟠

Likely Case

Privilege escalation to SMM level allowing attackers to bypass operating system security controls, install rootkits, and maintain persistence even after OS reinstallation.

🟢

If Mitigated

Limited impact if proper SMM protections are in place and the system is isolated, though the vulnerability still provides a significant attack surface.

🌐 Internet-Facing: MEDIUM
🏢 Internal Only: HIGH

🎯 Exploit Status

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

Exploitation requires local access or ability to execute code on the system. SMM vulnerabilities typically require sophisticated exploitation techniques.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 5.4: 05.47.01+, 5.5: 05.55.01+, 5.6: 05.62.01+, 5.7: 05.71.01+

Vendor Advisory: https://www.insyde.com/security-pledge/sa-2024018/

Restart Required: Yes

Instructions:

1. Contact your device manufacturer for updated firmware. 2. Download the appropriate firmware update. 3. Apply the firmware update following manufacturer instructions. 4. Reboot the system to complete the update.

🧯 If You Can't Patch

  • Restrict physical and administrative access to affected systems
  • Implement strict endpoint security controls and monitoring for suspicious SMM activity

🔍 How to Verify

Check if Vulnerable:

Check firmware version in UEFI/BIOS settings or using manufacturer-specific tools. Compare against affected version ranges.

Check Version:

Manufacturer-specific commands vary. Typically check in UEFI/BIOS settings or use 'dmidecode' on Linux or manufacturer utilities on Windows.

Verify Fix Applied:

Verify firmware version has been updated to patched versions: 5.4: 05.47.01+, 5.5: 05.55.01+, 5.6: 05.62.01+, 5.7: 05.71.01+

📡 Detection & Monitoring

Log Indicators:

  • Unexpected firmware update attempts
  • SMM-related errors or warnings in system logs
  • Unusual BIOS/UEFI configuration changes

Network Indicators:

  • Unusual outbound connections from firmware management interfaces

SIEM Query:

Search for firmware update events or SMM-related errors in system logs. Monitor for unexpected BIOS/UEFI configuration changes.

🔗 References

📤 Share & Export