dbcve.org
Msm8905 FirmwareOperating system · Qualcomm

CVE-2019-14012

HIGH · 7.5 CVSS v3.1 Published 2020-04-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
Possibility of null pointer deference as the array of video codecs from media info is referenced without null checking while processing SDP messages in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables in MSM8905, MSM8909, MSM8917, MSM8920, MSM8937, MSM8940, MSM8953, Nicobar, QCM2150, QM215, Rennell, SC7180, SC8180X, SDA845, SDM429, SDM439, SDM450, SDM632, SDM845, SDM850, SDX24, SM6150, SM7150, SM8150

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 confidence

A null pointer dereference vulnerability exists in the SDP message processing code. When processing Session Description Protocol messages, the video codec array from media info is accessed without first checking if it is null, leading to a potential crash or denial of service when a malformed SDP message is received.

MitigationImplement null pointer validation checks on the video codec array before dereferencing it during SDP message processing. This is a firmware-level fix requiring updates from Qualcomm or OEM vendors.

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
Msm8905 FirmwareOperating system
Affected:all versions
Msm8909 FirmwareOperating system
Affected:all versions
Msm8917 FirmwareOperating system
Affected:all versions
Msm8920 FirmwareOperating system
Affected:all versions
Msm8937 FirmwareOperating system
Affected:all versions
Msm8940 FirmwareOperating system
Affected:all versions
Msm8953 FirmwareOperating system
Affected:all versions
Nicobar 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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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
    Check the device specifications or use system commands (e.g., 'cat /proc/cpuinfo' on Android, or check FCC ID / hardware documentation) to determine the chipset variant
    Affected if The chipset is one of: Msm8905, Msm8909, Msm8917, Msm8920, Msm8937, Msm8940, Msm8953, or Nicobar
  2. Verify baseband firmware version
    Check the baseband or radio firmware version through device settings or diagnostic tools (e.g., 'AT+CGMR' command or under Settings > About Phone > Baseband version on Android)
    Affected if Any firmware version is present on an affected chipset - all versions are vulnerable
  3. Confirm SDP processing capability is active
    The device processes SDP messages when VoIP, video calling, or IMS (IP Multimedia Subsystem) services are enabled. Check if any VoIP or video calling applications are installed and active, or if IMS services are provisioned
    Affected if The device has active VoIP, video calling, or IMS functionality that processes SDP messages - the vulnerability triggers when malformed SDP is received during these operations
  4. Check for SDP handling component
    Examine the firmware or software stack for the presence of SDP message parsing modules in the baseband/RIL (Radio Interface Layer) or telephony services. This is typically part of the IMS/VoIP stack in mobile device firmware
    Affected if The device firmware contains SDP processing code for media negotiation - the vulnerable code path exists in all affected firmware versions

A device is affected if it uses any of the listed Qualcomm chipsets (Msm8905, Msm8909, Msm8917, Msm8920, Msm8937, Msm8940, Msm8953, Nicobar) and supports SDP message processing for VoIP, video calling, or IMS services, regardless of firmware version since all versions 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

Implement null pointer validation checks on the video codec array before dereferencing it during SDP message processing. This is a firmware-level fix requiring updates from Qualcomm or OEM vendors.

Fix this in Msm8905 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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