dbcve.org
Mdm9650 FirmwareOperating system · Qualcomm

CVE-2017-18142

CRITICAL · 9.8 CVSS v3.0 Published 2018-04-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
In Android before security patch level 2018-04-05 on Qualcomm Snapdragon Mobile MDM9650, MDM9655, SD 835, SD 845, SD 850, while processing the IMS SIP username, a buffer overflow can occur.

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 Qualcomm Snapdragon mobile chipsets (MDM9650, MDM9655, SD 835, SD 845, SD 850) when processing IMS SIP username data, potentially allowing remote code execution or service disruption.

MitigationApply Android security patch level 2018-04-05 or later to affected devices; this requires a vendor/carrier firmware update.

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
Mdm9650 FirmwareOperating system
Affected:all versions
Mdm9655 FirmwareOperating system
Affected:all versions
Sd 835 FirmwareOperating system
Affected:all versions
Sd 845 FirmwareOperating system
Affected:all versions
Sd 850 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
High
Integrity
High
Availability
High

CVSS:3.0/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 checks

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

  1. Identify the device chipset model
    Check /proc/cpuinfo for hardware identifier, or check device specifications in Settings > About Phone > Hardware info. Look for 'Snapdragon' or the specific model numbers MDM9650, MDM9655, SD 835, SD 845, or SD 850.
    Affected if The device uses a Qualcomm Snapdragon chipset from the affected list (MDM9650, MDM9655, SD 835, SD 845, SD 850).
  2. Check baseband modem firmware version
    View the baseband version in Settings > About Phone > Baseband version or by running 'getprop ro.baseband' or 'getprop gsm.version.baseband' via ADB shell.
    Affected if The baseband version corresponds to a chipset from the affected list. All firmware versions for these chipsets are affected.
  3. Confirm IMS VoLTE feature is active
    Check if the device has Voice over LTE (VoLTE) enabled. This can be found in Settings > Network & Internet > Mobile Network > Preferred Network Type, or check that IMS is registered via 'getprop net.rmnet0.ims.initialized' or similar IMS properties.
    Affected if IMS and VoLTE are actively used, as the vulnerability triggers when processing IMS SIP username data.
  4. Check Android security patch level
    View the Android security patch level in Settings > About Phone > Android security patch level, or run 'getprop ro.build.version.security_patch' via ADB shell.
    Affected if The security patch level is earlier than 2018-04-05, indicating the firmware has not been updated to mitigate this vulnerability.

The device is affected if it uses any of the listed Qualcomm Snapdragon chipsets (MDM9650, MDM9655, SD 835, SD 845, SD 850) and the Android security patch level is before 2018-04-05, with IMS/VoLTE functionality enabled.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Android security patch level 2018-04-05 or later to affected devices; this requires a vendor/carrier firmware update.

Recommended fix High confidence

Android with security patch level 2018-04-05 or later (contact device manufacturer for specific update)

  1. Check your current Android security patch level in Settings > About Phone > Software Information > Security patch level
  2. If the security patch level is earlier than April 5, 2018, check for a system update from your device manufacturer
  3. Download and install the latest available Android update that includes the April 2018 security patch level or later
  4. After updating, verify the security patch level now shows April 5, 2018 or later in Settings > About Phone > Software Information > Security patch level
Caveat Update availability depends on device manufacturer support; older devices may no longer receive security updates

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mdm9650 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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