CVE-2020-11167

9.8 CRITICAL

📋 TL;DR

This is a critical memory corruption vulnerability in Qualcomm Snapdragon chipsets' Bluetooth L2CAP reassembly logic. Attackers can remotely execute arbitrary code or cause denial of service by sending specially crafted Bluetooth packets that exceed expected data lengths. Affects numerous Qualcomm Snapdragon platforms across automotive, mobile, IoT, and wearable devices.

💻 Affected Systems

Products:
  • Snapdragon Auto
  • Snapdragon Compute
  • Snapdragon Connectivity
  • Snapdragon Consumer IOT
  • Snapdragon Industrial IOT
  • Snapdragon Mobile
  • Snapdragon Voice & Music
  • Snapdragon Wearables
Versions: Multiple chipset versions - see Qualcomm December 2020 bulletin for specific affected chipsets
Operating Systems: Android, Linux-based embedded systems
Default Config Vulnerable: ⚠️ Yes
Notes: Vulnerability exists in Bluetooth firmware/stack. All devices with affected Snapdragon chipsets and Bluetooth enabled are vulnerable by default.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Remote code execution with kernel privileges leading to complete device compromise, data theft, and persistent backdoor installation.

🟠

Likely Case

Remote denial of service (device crash/reboot) or limited code execution in Bluetooth context.

🟢

If Mitigated

Denial of service only if exploit attempts are blocked or fail due to mitigations.

🌐 Internet-Facing: MEDIUM
🏢 Internal Only: HIGH

🎯 Exploit Status

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

Exploitation requires Bluetooth proximity (typically within 10 meters). No authentication needed as Bluetooth pairing not required for this attack vector.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Refer to device manufacturer updates - patches released in December 2020

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

Restart Required: Yes

Instructions:

1. Check with device manufacturer for firmware/OS updates. 2. Apply latest security patches from device vendor. 3. Reboot device after update. 4. Verify Bluetooth stack version is patched.

🔧 Temporary Workarounds

Disable Bluetooth

all

Turn off Bluetooth when not in use to prevent remote exploitation

adb shell settings put global bluetooth_on 0
systemctl stop bluetooth (Linux)
Turn off in device settings

Restrict Bluetooth Visibility

all

Set Bluetooth to non-discoverable mode to reduce attack surface

adb shell settings put global bluetooth_discoverability 0
hciconfig hci0 noscan

🧯 If You Can't Patch

  • Segment affected devices on separate network/VLAN
  • Implement Bluetooth usage policies restricting to trusted devices only

🔍 How to Verify

Check if Vulnerable:

Check device chipset model and firmware version against Qualcomm advisory. Use: adb shell getprop ro.boot.hardware.sku or check device specifications.

Check Version:

adb shell getprop ro.build.version.security_patch

Verify Fix Applied:

Verify device has December 2020 or later security patches installed. Check Bluetooth stack version if available from manufacturer.

📡 Detection & Monitoring

Log Indicators:

  • Bluetooth stack crashes
  • Kernel panic logs
  • Unexpected Bluetooth disconnections

Network Indicators:

  • Unusual Bluetooth packet patterns
  • Multiple connection attempts from unknown devices

SIEM Query:

source="bluetooth" AND (event="crash" OR event="panic")

🔗 References

📤 Share & Export