dbcve.org
Sd 835 FirmwareOperating system · Qualcomm

CVE-2018-11882

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 controller 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 · high confidence

This is an incorrect bounds check vulnerability in the WLAN controller firmware of Qualcomm Snapdragon mobile processors (SD 835, SD 845, SD 850, SDA660). The improper bounds validation can allow a buffer overwrite, potentially enabling code execution or denial of service in the wireless component.

MitigationApply the Qualcomm firmware patch (typically delivered through device OEM updates) to address the bounds check error in the WLAN controller; until the patch is available, monitor wireless traffic for anomalous behavior as a compensating control.

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 Qualcomm Snapdragon chip model
    Check device specifications or system information to determine if the device uses Snapdragon SD 835, SD 845, SD 850, or SDA.mobile (SDA660). On Android, this may appear in Settings > About Phone > Processor or in /proc/cpuinfo.
    Affected if The device contains any of these specific Snapdragon variants (SD 835, SD 845, SD 850, SDA660)
  2. Verify WLAN controller is enabled
    Confirm the wireless interface is active. On Android, check that Wi-Fi is turned on; on Linux systems, run 'iwconfig' or check that wlan0 interface exists and is up.
    Affected if WLAN functionality is enabled and the vulnerable firmware is running
  3. Determine WLAN firmware version
    Attempt to retrieve the WLAN firmware version. On Android, this may be visible in diagnostic menus or via 'dmesg | grep wlan' or '/system/bin/iw list'. The exact method varies by device OEM and Android version.
    Affected if The WLAN firmware version cannot be determined or is earlier than the OEM patch date
  4. Check OEM security patch level
    On Android devices, go to Settings > About Phone > Security Patch Level to see the installed security update. Compare the date to when the CVE was publicly disclosed (June 2018) and when your OEM released fixes.
    Affected if The Security Patch Level predates June 2018 or the device has not received OEM firmware updates since the CVE was published
  5. Confirm device is not receiving firmware updates
    Check with the device manufacturer (OEM) website or support to verify whether the specific device model has received a firmware update addressing this WLAN bounds check vulnerability.
    Affected if The OEM has not released or deployed a firmware patch for CVE-2018-11882 to your device model

A user is affected if their device contains a Snapdragon SD 835, SD 845, SD 850, or SDA660 chip and the WLAN firmware has not been updated by the OEM with the bounds check fix.

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 the Qualcomm firmware patch (typically delivered through device OEM updates) to address the bounds check error in the WLAN controller; until the patch is available, monitor wireless traffic for anomalous behavior as a compensating control.

Fix this in Sd 835 Firmware Scoped from the published advisory
  • Consultation12.0 h
  • Implementation4.0 h
  • Testing16.0 h
  • Review / QA8.0 h
40.0 hours of engineering $6,960
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-11882 — 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-11882 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