CVE-2019-14027
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 due to lack of upper bound check on channel length which is used for a loop. in Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking in APQ8098, IPQ6018, IPQ8074, MSM8998, Nicobar, QCA8081, QCN7605, QCS404, QCS605, Rennell, SC8180X, SDA660, SDA845, SDM630, SDM636, SDM660, SDM670, SDM710, SDM845, SDM850, SM6150, SM7150, SM8150, SXR1130, 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 · high confidenceBuffer overflow vulnerability in Snapdragon SoC firmware where channel length used in a loop iteration count lacks proper upper bound validation. An attacker could potentially overflow a buffer by providing an excessively large channel length value, leading to memory corruption and potential code execution.
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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/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 SoC modelCheck the device hardware specifications, system information, or boot logs to determine the Qualcomm Snapdragon SoC model (e.g., Apq8098, Ipq6018, Ipq8074, Msm8998, Nicobar, Qca8081, Qcn7605, Qcs404)Affected if The device uses any of the following SoCs: Apq8098, Ipq6018, Ipq8074, Msm8998, Nicobar, Qca8081, Qcn7605, or Qcs404
-
Confirm firmware versionRetrieve the firmware version from the device via CLI (e.g., 'cat /proc/version', 'version', or OEM-specific command) or by inspecting firmware image metadataAffected if Firmware version is present, as all versions of the affected SoCs are vulnerable
-
Identify network services handling channel parametersExamine running network services or daemon logs that process wireless/radio channel configuration parameters, particularly those that may accept channel length valuesAffected if The device runs network services that accept channel length input from untrusted sources
-
Check for vendor firmware update availabilityConsult the device vendor or Qualcomm product security bulletins for available patches for the specific SoC modelAffected if No vendor patch has been applied to address the bounds checking issue in channel length processing
If your device incorporates any of the affected Qualcomm SoC models (Apq8098, Ipq6018, Ipq8074, Msm8998, Nicobar, Qca8081, Qcn7605, or Qcs404) and processes channel length values through network-facing interfaces, you are potentially affected by this buffer overflow 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 vendor-supplied firmware updates from Qualcomm/OEMs that include proper bounds checking on channel length values before loop execution. Until patches are available, consider network-level mitigations to reduce attack surface for affected devices.
- Consultation8.0 h
- Implementation16.0 h
- Testing24.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 $16,384.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-14027 — 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-14027 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