CVE-2021-30350

8.4 HIGH

📋 TL;DR

This vulnerability in Qualcomm Snapdragon chipsets allows memory corruption due to insufficient validation of MBN header size against input buffer. Attackers could potentially execute arbitrary code or cause denial of service on affected devices. It impacts various Snapdragon platforms including automotive, compute, connectivity, consumer IoT, industrial IoT, and wearables.

💻 Affected Systems

Products:
  • Snapdragon Auto
  • Snapdragon Compute
  • Snapdragon Connectivity
  • Snapdragon Consumer IOT
  • Snapdragon Industrial IOT
  • Snapdragon Wearables
Versions: Specific chipset versions not detailed in bulletin, but affected by firmware versions prior to April 2022 patches
Operating Systems: Android-based systems and embedded OS using affected Snapdragon chipsets
Default Config Vulnerable: ⚠️ Yes
Notes: Affects devices using vulnerable Qualcomm firmware/baseband implementations. Exact chip models not specified in public bulletin.

📦 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 or instability, potentially requiring physical reset.

🟢

If Mitigated

Limited impact with proper network segmentation and security controls in place.

🌐 Internet-Facing: MEDIUM
🏢 Internal Only: HIGH

🎯 Exploit Status

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

Memory corruption vulnerabilities in baseband/firmware components typically require specialized knowledge but can be exploited via crafted network packets or local access.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Firmware updates released in April 2022 security bulletin

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

Restart Required: Yes

Instructions:

1. Contact device manufacturer for firmware updates. 2. Apply Qualcomm-provided patches through OEM update channels. 3. Reboot device after update installation.

🔧 Temporary Workarounds

Network segmentation

all

Isolate affected devices from untrusted networks to limit attack surface

Access control restrictions

all

Implement strict network access controls and firewall rules for affected devices

🧯 If You Can't Patch

  • Segment affected devices in isolated network zones with strict ingress/egress filtering
  • Implement monitoring for abnormal device behavior or crashes that could indicate exploitation attempts

🔍 How to Verify

Check if Vulnerable:

Check device firmware/baseband version against manufacturer's security bulletin. For Android devices: Settings > About phone > Baseband version

Check Version:

Android: adb shell getprop gsm.version.baseband | Linux-based: dmesg | grep -i baseband

Verify Fix Applied:

Verify firmware version has been updated to post-April 2022 release and check for absence of related crashes in system logs

📡 Detection & Monitoring

Log Indicators:

  • Kernel panics
  • Baseband processor crashes
  • Unexpected device reboots
  • Memory corruption errors in system logs

Network Indicators:

  • Unusual baseband communication patterns
  • Malformed MBN packets to affected devices

SIEM Query:

Device logs containing 'panic', 'crash', 'corruption' OR network traffic to baseband ports with abnormal packet sizes

🔗 References

📤 Share & Export