dbcve.org
Mdm9615 FirmwareOperating system · Qualcomm

CVE-2017-18329

HIGH · 7.8 CVSS v3.0 Published 2019-01-03
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
Possible Buffer overflow when transmitting an RTP packet in snapdragon automobile and snapdragon wear in versions MDM9615, MDM9625, MDM9635M, MDM9640, MDM9645, MDM9650, MDM9655, MSM8909W, MSM8996AU, SD 210/SD 212/SD 205, SD 425, SD 427, SD 430, SD 435, SD 450, SD 615/16/SD 415, SD 625, SD 636, SD 650/52, SD 712 / SD 710 / SD 670, SD 810, SD 820, SD 835, SD 845 / SD 850, SDA660, SDM630, SDM660, Snapdragon_High_Med_2016, SXR1130

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

Buffer overflow vulnerability in RTP (Real-time Transport Protocol) packet transmission code within Qualcomm Snapdragon chipset firmware. The flaw allows potential code execution or denial of service when processing malformed RTP packets, affecting multiple mobile and automotive processor variants.

MitigationApply Qualcomm firmware/security patches for affected Snapdragon versions; implement input validation on RTP packet handlers; restrict network exposure of affected devices where possible.

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
Mdm9615 FirmwareOperating system
Affected:all versions
Mdm9625 FirmwareOperating system
Affected:all versions
Mdm9635m FirmwareOperating system
Affected:all versions
Mdm9640 FirmwareOperating system
Affected:all versions
Mdm9645 FirmwareOperating system
Affected:all versions
Mdm9650 FirmwareOperating system
Affected:all versions
Mdm9655 FirmwareOperating system
Affected:all versions
Msm8909w 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.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 checks

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

  1. Identify the Qualcomm chipset model
    Determine the specific Qualcomm Snapdragon or modem chipset present in the device. This can be done by reviewing device hardware specifications, using system information commands (such as 'cat /proc/cpuinfo' on Android or checking BIOS/UEFI information), or reviewing device documentation. Match the chipset identifier against the list: Mdm9615, Mdm9625, Mdm9635m, Mdm9640, Mdm9645, Mdm9650, Mdm9655, or Msm8909w.
    Affected if The device contains any of the following chipsets: Mdm9615, Mdm9625, Mdm9635m, Mdm9640, Mdm9645, Mdm9650, Mdm9655, or Msm8909w.
  2. Verify firmware version
    Retrieve the firmware version of the identified Qualcomm chipset. On mobile devices, this is typically found in Settings > About Phone > Build Number, or via AT commands on modem interfaces (such as 'AT+CGMR' or 'AT+QMSV'). Compare the installed firmware version against the affected product list.
    Affected if The chipset firmware is any version of the listed affected products (all versions are impacted).
  3. Confirm RTP functionality is enabled
    Determine whether the Real-time Transport Protocol (RTP) is in use on the device. Check if VoIP, video conferencing, streaming applications, or other services that utilize RTP are installed and active. Review network configuration for RTP port usage (typically ports 5000-6000 UDP/RTP). Inspect running processes for RTP-related services.
    Affected if RTP packet processing is enabled or any application utilizing RTP is active on the device.
  4. Assess network exposure
    Evaluate whether the device is exposed to untrusted networks where malformed RTP packets could be received. Check firewall rules, network segmentation, and whether the device communicates over public networks or receives RTP traffic from external sources. Review inbound UDP port configurations.
    Affected if The device can receive RTP packets from untrusted or external network sources.

A user is affected if their device contains any of the listed Qualcomm chipsets (Mdm9615, Mdm9625, Mdm9635m, Mdm9640, Mdm9645, Mdm9650, Mdm9655, or Msm8909w) and has RTP functionality enabled with potential network exposure to malformed RTP packets.

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 Qualcomm firmware/security patches for affected Snapdragon versions; implement input validation on RTP packet handlers; restrict network exposure of affected devices where possible.

Fix this in Mdm9615 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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 locally
dbcve dependency scanner

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