CVE-2019-10532

9.8 CRITICAL

📋 TL;DR

A null-pointer dereference vulnerability in Qualcomm Snapdragon chipsets allows attackers to cause denial of service or potentially execute arbitrary code by triggering a crash when processing zero-length strings. This affects numerous Qualcomm-based devices across automotive, IoT, mobile, and wearable platforms.

💻 Affected Systems

Products:
  • Snapdragon Auto
  • Snapdragon Connectivity
  • Snapdragon Consumer IOT
  • Snapdragon Industrial IOT
  • Snapdragon IoT
  • Snapdragon Mobile
  • Snapdragon Voice & Music
  • Snapdragon Wearables
Versions: All versions prior to January 2020 security patches
Operating Systems: Android, Linux-based embedded systems
Default Config Vulnerable: ⚠️ Yes
Notes: Affects specific chipset models: APQ8009, APQ8017, APQ8053, APQ8064, APQ8096AU, APQ8098, MDM9206, MDM9207C, MDM9607, MSM8905, MSM8909, MSM8909W, MSM8917, MSM8920, MSM8937, MSM8939, MSM8940, MSM8953, MSM8996, Nicobar, QCS605, QM215, SDA660, SDA845, SDM429, SDM429W, SDM439, SDM450, SDM630, SDM632, SDM636, SDM660, SDM670, SDM710, SDM845, SDX20, SM6150, SM8150, SM8250, SXR1130, SXR2130

📦 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

Denial of service causing device crashes, reboots, or instability affecting functionality.

🟢

If Mitigated

Limited impact with proper network segmentation and exploit mitigations in place.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

CVSS 9.8 indicates critical severity with network-accessible attack vector. No public exploit code available at disclosure.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: January 2020 security patch level or later

Vendor Advisory: https://www.qualcomm.com/company/product-security/bulletins/january-2020-bulletin

Restart Required: Yes

Instructions:

1. Check device manufacturer for available firmware updates. 2. Apply January 2020 or later security patches. 3. Reboot device after update. 4. Verify patch installation.

🔧 Temporary Workarounds

Network segmentation

all

Isolate affected devices from untrusted networks to reduce attack surface

Input validation

all

Implement application-level validation to reject zero-length strings in vulnerable functions

🧯 If You Can't Patch

  • Segment affected devices in isolated network zones with strict access controls
  • Implement monitoring for abnormal crashes or reboots of affected devices

🔍 How to Verify

Check if Vulnerable:

Check device firmware version and security patch level. If before January 2020, device is vulnerable.

Check Version:

On Android: Settings > About phone > Android security patch level

Verify Fix Applied:

Confirm security patch level is January 2020 or later in device settings.

📡 Detection & Monitoring

Log Indicators:

  • Kernel panic logs
  • Unexpected device reboots
  • Null pointer exception in system logs

Network Indicators:

  • Unusual network traffic to device management interfaces
  • Protocol anomalies triggering string processing

SIEM Query:

source="device_logs" AND ("kernel panic" OR "null pointer" OR "segmentation fault")

🔗 References

📤 Share & Export