CVE-2024-33042

7.8 HIGH

📋 TL;DR

CVE-2024-33042 is a memory corruption vulnerability in Qualcomm chipsets that occurs when the Alternative Frequency offset value is set to 255. This could allow attackers to execute arbitrary code or cause denial of service on affected devices. The vulnerability affects devices using Qualcomm chipsets with vulnerable firmware.

💻 Affected Systems

Products:
  • Qualcomm chipsets with vulnerable firmware
Versions: Specific firmware versions not publicly detailed in advisory
Operating Systems: Android, embedded systems using Qualcomm chipsets
Default Config Vulnerable: ⚠️ Yes
Notes: Affects devices with Qualcomm chipsets that have the vulnerable firmware component. Exact device models depend on OEM implementation.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Remote code execution leading to complete device compromise, data theft, or persistent backdoor installation.

🟠

Likely Case

Device crash or reboot causing denial of service, potentially requiring physical reset.

🟢

If Mitigated

Limited impact if proper network segmentation and access controls prevent exploitation attempts.

🌐 Internet-Facing: MEDIUM - Requires specific conditions and network access to trigger, but could affect exposed devices.
🏢 Internal Only: LOW - Exploitation requires network access to vulnerable services, typically limited to internal networks.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ⚠️ Yes
Complexity: MEDIUM

Exploitation requires sending specially crafted network packets to trigger the memory corruption condition.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Refer to Qualcomm September 2024 security bulletin for specific patched versions

Vendor Advisory: https://docs.qualcomm.com/product/publicresources/securitybulletin/september-2024-bulletin.html

Restart Required: Yes

Instructions:

1. Check Qualcomm advisory for affected chipset models. 2. Contact device manufacturer for firmware updates. 3. Apply manufacturer-provided firmware patches. 4. Reboot device after patching.

🔧 Temporary Workarounds

Network segmentation

all

Isolate devices with Qualcomm chipsets from untrusted networks

Access control restrictions

all

Implement firewall rules to restrict network access to vulnerable services

🧯 If You Can't Patch

  • Segment affected devices in isolated network zones
  • Implement strict network access controls and monitoring

🔍 How to Verify

Check if Vulnerable:

Check device firmware version against Qualcomm's advisory and manufacturer security updates

Check Version:

Device-specific commands vary by manufacturer (e.g., Android: Settings > About phone > Build number)

Verify Fix Applied:

Verify firmware version has been updated to patched version from manufacturer

📡 Detection & Monitoring

Log Indicators:

  • Unexpected device reboots
  • Memory-related crash logs
  • Network traffic with specific offset values

Network Indicators:

  • Unusual network packets targeting Qualcomm-specific services
  • Traffic with Alternative Frequency offset manipulation

SIEM Query:

Search for network traffic patterns matching Qualcomm chipset communication with offset value 255

🔗 References

📤 Share & Export