CVE-2018-11874
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 · uneditedBuffer overflow if the length of passphrase is more than 32 when setting up secure NDP connection 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 confidenceBuffer overflow vulnerability in Qualcomm Snapdragon mobile chipsets (SD 835, SD 845, SD 850, SDA660) where passing a passphrase exceeding 32 characters during secure NDP (Neighbor Discovery Protocol) connection setup causes a buffer overflow, potentially leading to code execution or denial of service.
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 dataall versionsall versionsall versionsall versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device chipset modelCheck the device specifications or system information to determine if the Qualcomm Snapdragon SD 835, SD 845, SD 850, or SDA660 chipset is present. This can be done via device info settings, kernel logs (/proc/cpuinfo), or baseband firmware identification.Affected if The device contains any of the following chipsets: SD 835, SD 845, SD 850, or SDA660
-
Verify baseband processor firmware versionQuery the baseband processor firmware version through device engineering mode, AT commands, or system logs. On Android, check /proc/version or baseband-related entries in /proc/.Affected if All firmware versions on the affected chipsets are vulnerable; no patched version exists for these models
-
Check if NDP (Neighbor Discovery Protocol) is configuredExamine network configuration settings, particularly any NDP-related or neighbor discovery protocol settings. Look for secure NDP connection configurations in network management interfaces or configuration files.Affected if Secure NDP connections are configured and active on the device
-
Inspect NDP passphrase configurationReview the passphrase or PSK (Pre-Shared Key) configured for secure NDP connections. Access this through network security settings, NDP configuration panels, or by examining the configuration files where NDP credentials are stored.Affected if A passphrase exceeding 32 characters is configured for secure NDP connections
A user is affected if their device uses a Qualcomm Snapdragon SD 835, SD 845, SD 850, or SDA660 chipset and has secure NDP connections configured with passphrases longer than 32 characters.
Generated from the published advisory. Verify against your own configuration.
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 dataApply firmware/security updates from device OEMs that include Qualcomm's patched baseband processor firmware; until patched, avoid using passphrases longer than 32 characters for secure NDP connections.
- Consultation12.0 h
- Implementation4.0 h
- Testing16.0 h
- Review / QA12.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,288.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-11874 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-11874 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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