CVE-2024-45555

8.4 HIGH

📋 TL;DR

This vulnerability allows attackers to bypass boot verification by overwriting an already verified IFS2 image, enabling injection of unauthorized programs into security-sensitive images. This could lead to booting tampered system images, compromising device integrity. Affects Qualcomm devices using IFS2 boot images.

💻 Affected Systems

Products:
  • Qualcomm chipsets with IFS2 bootloader
Versions: Specific versions not publicly detailed in advisory
Operating Systems: Android, Linux-based systems using Qualcomm chips
Default Config Vulnerable: ⚠️ Yes
Notes: Affects devices with IFS2 boot images; exact chipset models not specified in public advisory.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete device compromise allowing persistent malware installation at boot level, enabling surveillance, data theft, or device bricking.

🟠

Likely Case

Boot-level persistence for targeted attacks, allowing attackers to maintain control even after system resets.

🟢

If Mitigated

Limited impact if secure boot is properly implemented with hardware-backed verification.

🌐 Internet-Facing: LOW - Requires physical or privileged access to device for exploitation.
🏢 Internal Only: MEDIUM - Could be exploited by malicious insiders or through compromised management systems.

🎯 Exploit Status

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

Requires ability to modify boot images, typically needing elevated privileges or physical access.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Refer to Qualcomm January 2025 security bulletin

Vendor Advisory: https://docs.qualcomm.com/product/publicresources/securitybulletin/january-2025-bulletin.html

Restart Required: Yes

Instructions:

1. Check device manufacturer for firmware updates. 2. Apply Qualcomm-provided patches through OEM updates. 3. Verify bootloader integrity after update.

🔧 Temporary Workarounds

Secure Boot Enforcement

all

Ensure secure boot is enabled and properly configured to verify boot images.

🧯 If You Can't Patch

  • Restrict physical access to devices
  • Implement strict access controls for device management systems

🔍 How to Verify

Check if Vulnerable:

Check device bootloader version against Qualcomm security bulletin; consult device manufacturer for specific vulnerability status.

Check Version:

Device-specific commands vary by manufacturer; typically through fastboot or device settings.

Verify Fix Applied:

Verify bootloader version has been updated per manufacturer instructions; check for January 2025 security patches.

📡 Detection & Monitoring

Log Indicators:

  • Unexpected bootloader modifications
  • Failed secure boot attempts
  • Boot image verification failures

Network Indicators:

  • Unusual device management traffic
  • Unexpected firmware update attempts

SIEM Query:

Search for boot-related errors or verification failures in system logs.

🔗 References

📤 Share & Export