dbcve.org
Mdm9206 FirmwareOperating system · Qualcomm

CVE-2019-14051

HIGH · 7.8 CVSS v3.1 Published 2020-02-07
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
Subsequent additions performed during Module loading while allocating the memory would lead to integer overflow and then to buffer overflow in Snapdragon Industrial IOT in MDM9206, MDM9607

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

A memory allocation integer overflow vulnerability exists in the module loading functionality of Qualcomm Snapdragon Industrial IOT chipsets (MDM9206, MDM9607). During memory allocation for module loading, subsequent additions overflow the integer size limit, resulting in an undersized buffer allocation that subsequently leads to a buffer overflow when data is written to it.

MitigationApply the vendor-provided firmware/security patch for CVE-2019-14051 from the device manufacturer. If no patch is available, segregate affected devices on isolated network segments and monitor for exploitation indicators.

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
Mdm9206 FirmwareOperating system
Affected:all versions
Mdm9607 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.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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Qualcomm chipset model
    Review device hardware specifications, datasheet, or boot logs to confirm the exact chipset variant (MDM9206 or MDM9607). On Linux-based devices, check /proc/cpuinfo, /sys/devices/system/cpu/, or debug UART output for chipset identification strings.
    Affected if The device uses a Qualcomm MDM9206 or MDM9607 chipset in the Snapdragon Industrial IOT line.
  2. Verify firmware version
    Retrieve the firmware version through vendor-specific interfaces (AT commands, diagnostic ports, debug shells, or manufacturer management portals). Compare against the base firmware release for the MDM9206 or MDM9607.
    Affected if The device runs any firmware version on the MDM9206 or MDM9607 (all versions are affected per the CVE scope).
  3. Confirm module loading capability is present
    Identify whether the device exposes module loading functionality (firmware module injection, peripheral module provisioning, or diagnostic module update interfaces). Check for related kernel modules, firmware loading daemons, or vendor-specific module management tools.
    Affected if The module loading feature is enabled and accessible on the affected chipset.
  4. Assess network exposure of module loading interfaces
    Audit network services, USB debugging interfaces, and diagnostic ports for exposure to untrusted networks. Review firewall rules and access control lists protecting firmware update or module loading endpoints.
    Affected if Module loading interfaces are reachable from network segments without strict access controls.
  5. Check for isolation from sensitive network segments
    Review network topology and VLAN configuration to determine if the device is placed on isolated network segments separate from critical infrastructure or sensitive data flows.
    Affected if The affected device shares network proximity with production systems without segmentation.

The environment is affected if any device runs on a Qualcomm MDM9206 or MDM9607 chipset with module loading functionality enabled and accessible, regardless of firmware version.

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 vendor-provided firmware/security patch for CVE-2019-14051 from the device manufacturer. If no patch is available, segregate affected devices on isolated network segments and monitor for exploitation indicators.

Fix this in Mdm9206 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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