dbcve.org
Sd 845 FirmwareOperating system · Qualcomm

CVE-2018-11862

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
Buffer overflow can happen in WLAN module due to lack of validation of the input length in Snapdragon Mobile in version 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

Buffer overflow vulnerability in the WLAN module of Snapdragon SD 845, SD 850, and SDA660 processors caused by missing input length validation. This could allow an attacker to overwrite memory boundaries, potentially achieving code execution or causing denial of service.

MitigationApply Qualcomm OEM firmware patches when available; until then, restrict WLAN exposure and monitor for indicators of compromise. No user-facing mitigation available for end-of-life devices.

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 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 device specifications or system information to determine the exact Snapdragon processor model (e.g., via 'Settings > About Phone' on Android, or lscpu/mobile-info on Linux-based systems)
    Affected if The chipset is Snapdragon SD 845, SD 850, or SDA660
  2. Confirm WLAN firmware is in use
    Verify that the device utilizes the WLAN (Wi-Fi) module - check if Wi-Fi functionality is present and active on the device
    Affected if Wi-Fi is enabled and the device uses the vulnerable WLAN firmware module
  3. Check for OEM firmware patch availability
    Contact the device manufacturer or check their support website for firmware/security patch release notes related to this CVE
    Affected if No vendor firmware patch has been released or applied for this specific vulnerability

The environment is affected if the device contains a Snapdragon SD 845, SD 850, or SDA660 chipset and the WLAN module is in use, since all firmware versions of these chipsets are vulnerable.

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 Qualcomm OEM firmware patches when available; until then, restrict WLAN exposure and monitor for indicators of compromise. No user-facing mitigation available for end-of-life devices.

Fix this in Sd 845 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation40.0 h
  • Testing24.0 h
  • Review / QA16.0 h
88.0 hours of engineering $15,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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