CVE-2021-35100

7.5 HIGH

📋 TL;DR

This vulnerability is a buffer over-read in Qualcomm Snapdragon chipsets when parsing ID3 tags in media files. It allows attackers to read memory beyond allocated buffers, potentially exposing sensitive information. Affected devices include smartphones, wearables, automotive systems, and IoT devices using vulnerable Snapdragon components.

💻 Affected Systems

Products:
  • Snapdragon Auto
  • Snapdragon Compute
  • Snapdragon Connectivity
  • Snapdragon Consumer IOT
  • Snapdragon Industrial IOT
  • Snapdragon Mobile
  • Snapdragon Voice & Music
  • Snapdragon Wearables
Versions: Specific chipset versions not detailed in bulletin; check Qualcomm advisory for exact affected silicon revisions.
Operating Systems: Android, Linux-based embedded systems, Automotive OS variants
Default Config Vulnerable: ⚠️ Yes
Notes: Vulnerability is in firmware/driver layer, affecting multiple device types across Qualcomm's product lines. Exact impact depends on how media parsing is implemented in each device.

📦 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

Information disclosure through memory leaks, potentially exposing sensitive data like encryption keys or user information.

🟢

If Mitigated

Denial of service through application crashes or limited information disclosure if memory protections are enabled.

🌐 Internet-Facing: MEDIUM - Requires processing malicious media files, which could come from untrusted sources like downloads or messaging apps.
🏢 Internal Only: LOW - Primarily affects client devices rather than internal infrastructure servers.

🎯 Exploit Status

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

Exploitation requires crafting malicious media files with specially crafted ID3 tags. No public exploit code is known, but the vulnerability is in widely deployed hardware.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Refer to device manufacturer updates - Qualcomm has provided fixes to OEM partners.

Vendor Advisory: https://www.qualcomm.com/company/product-security/bulletins/april-2022-bulletin

Restart Required: Yes

Instructions:

1. Check with device manufacturer for security updates. 2. Apply available firmware/OS updates. 3. For embedded systems, contact Qualcomm or OEM for patched firmware images. 4. Reboot device after update installation.

🔧 Temporary Workarounds

Restrict media file sources

all

Limit media file processing to trusted sources only

Disable automatic media parsing

all

Configure applications to not automatically parse media metadata

🧯 If You Can't Patch

  • Network segmentation to isolate vulnerable devices from untrusted networks
  • Implement application allowlisting to restrict which apps can process media files

🔍 How to Verify

Check if Vulnerable:

Check device firmware version against manufacturer security bulletins. Use 'getprop ro.build.fingerprint' on Android devices to check build information.

Check Version:

Android: 'getprop ro.build.version.security_patch' or 'getprop ro.vendor.build.security_patch'

Verify Fix Applied:

Verify security patch level is April 2022 or later. Check for Qualcomm security bulletin mentions in update notes.

📡 Detection & Monitoring

Log Indicators:

  • Media application crashes
  • Kernel panic logs related to audio/video processing
  • Memory access violation errors

Network Indicators:

  • Unusual media file downloads from suspicious sources
  • Multiple failed media parsing attempts

SIEM Query:

Process crashes with module names containing 'audio', 'media', or 'qcom' combined with memory access violation error codes

🔗 References

📤 Share & Export