CVE-2019-14111
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 · uneditedPossible buffer overflow while handling NAN reception of NMF in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking in IPQ6018, IPQ8074, Nicobar, QCA6390, QCA8081, QCN7605, QCS404, QCS405, Rennell, SC7180, SC8180X, SM6150, SM7150, SM8150, SXR2130
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 confidenceBuffer overflow vulnerability in the NAN (Neighbor Awareness Networking) NMF reception handler across multiple Qualcomm Snapdragon chipset families. The flaw could allow remote attackers to execute arbitrary code or cause denial of service due to improper bounds checking when processing NAN protocol messages.
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 versionsall 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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, system information, or boot logs for the Qualcomm chipset identifier (e.g., ipq6018, ipq8074, qca6390, qcs405, etc.)Affected if The chipset matches any of the following: Ipq6018, Ipq8074, Nicobar, Qca6390, Qca8081, Qcn7605, Qcs404, or Qcs405
-
Confirm the firmware versionRetrieve the firmware version from the device system settings, bootloader, or via command such as 'cat /proc/version', 'uname -a', or the device's web interface firmware info pageAffected if The firmware version is present and corresponds to one of the affected chipset families listed above (all versions are vulnerable)
-
Verify if NAN (Neighbor Awareness Networking) feature is enabledCheck the device wireless or network configuration settings for NAN/Neighbor Awareness Networking. On Linux-based devices, run 'iw list' or check for 'nan' in interface listings via 'ip link show' or 'iw dev'Affected if NAN interface is listed (e.g., 'nan0') or NAN feature is enabled in the device configuration
-
Inspect NAN protocol message handlingMonitor network traffic or check system logs for NAN-related messages. Use packet capture tools if NAN traffic is being processed, or review kernel logs for NAN handler activityAffected if The device is actively processing NAN protocol frames and the firmware remains unpatched (vulnerable)
-
Check for available firmware updatesConsult the device manufacturer documentation, support website, or firmware changelog to determine if a security patch addressing this CVE has been releasedAffected if No firmware update addressing CVE-2019-14111 has been applied, and the device uses an affected chipset with NAN enabled
A device is affected if it uses any of the listed Qualcomm chipset families (Ipq6018, Ipq8074, Nicobar, Qca6390, Qca8081, Qcn7605, Qcs404, Qcs405) with NAN feature enabled and lacks the vendor security patch for this vulnerability.
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 Qualcomm-provided firmware patches to affected chipsets; contact device manufacturers for available updates. Network-level filtering of malicious NAN frames may provide interim mitigation until firmware updates are deployed.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-14111 — 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-2019-14111 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