dbcve.org
Sd 835 FirmwareOperating system · Qualcomm

CVE-2018-11880

HIGH · 7.8 CVSS v3.0 Published 2018-10-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Incorrect bound check can lead to potential buffer overwrite in WLAN function in Snapdragon Mobile in version SD 835, SD 845, SD 850, SDA660.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

An incorrect bound check in the WLAN function of Qualcomm Snapdragon processors (SD 835, SD 845, SD 850, SDA660) can lead to a buffer overwrite vulnerability. This local privilege escalation issue in WiFi firmware could allow an attacker to overwrite memory beyond allocated buffers.

MitigationApply firmware updates from Qualcomm and device manufacturers to patch the bound check vulnerability in the WLAN function. Until patches are available, minimize WiFi attack surface by disabling WiFi in sensitive environments.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Sd 835 FirmwareOperating system
Affected:all versions
Sd 845 FirmwareOperating system
Affected:all versions
Sd 850 FirmwareOperating system
Affected:all versions
Sda660 FirmwareOperating system
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the processor chipset model
    Check system information or device specifications to determine the exact Qualcomm Snapdragon model number (SD 835, SD 845, SD 850, or SDA660). On Android, this is typically found in Settings > About Phone > Processor or via commands like 'cat /proc/cpuinfo' or 'getprop ro.hardware'. On other platforms, check BIOS/UEFI or system documentation.
    Affected if The chipset is one of: SD 835, SD 845, SD 850, or SDA660.
  2. Confirm WiFi is enabled
    Check if the wireless interface is active. On Linux, use 'iwconfig' or 'ip link show'. On Android, check Settings > Network & Internet > WiFi or use 'settings get global wifi_on'. On Windows, check adapter status in Device Manager or Network Connections.
    Affected if WiFi is turned on or the wireless adapter is enabled.
  3. Check WLAN firmware version
    Retrieve the WLAN firmware version from the wireless driver. On Linux, use 'ethtool -i wlan0' or 'modinfo <wireless_driver>'. On Android, try 'cat /sys/class/net/wlan0/firmware_version' or check via 'dmesg' output for firmware loading messages.
    Affected if The firmware version belongs to an affected Snapdragon model (SD 835, SD 845, SD 850, SDA660) regardless of version number, as all versions are vulnerable.
  4. Verify the WLAN driver is loaded
    Confirm the wireless network interface exists and is operational. Use 'ip link show' or 'ifconfig -a' to list network interfaces. Check for wlan0, wlan1, or similar wireless interfaces. On Android, verify via 'netstat -i' or 'ip addr'.
    Affected if A wireless interface (wlan0, etc.) exists and is UP, indicating the WLAN function is active.

The device is affected if it uses a Qualcomm Snapdragon SD 835, SD 845, SD 850, or SDA660 chipset and has WiFi functionality enabled, as all firmware versions of these processors contain the bound check vulnerability in the WLAN function.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply firmware updates from Qualcomm and device manufacturers to patch the bound check vulnerability in the WLAN function. Until patches are available, minimize WiFi attack surface by disabling WiFi in sensitive environments.

Fix this in Sd 835 Firmware Scoped from the published advisory
  • Consultation16.0 h
  • Implementation24.0 h
  • Testing12.0 h
  • Review / QA8.0 h
60.0 hours of engineering $10,760
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $17,216.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-11880 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-11880 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data