dbcve.org
Mdm9206 FirmwareOperating system · Qualcomm

CVE-2015-9139

CRITICAL · 9.8 CVSS v3.0 Published 2018-04-18
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 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Mobile and Snapdragon Wear MDM9206, MDM9607, MDM9615, MDM9625, MDM9635M, MDM9640, MDM9645, MDM9655, MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 425, SD 430, SD 615/16/SD 415, SD 617, SD 650/52, SD 800, SD 808, SD 810, and SD 820, improper input validation can occur while negotiating an SSL handshake.

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

Improper input validation in the SSL handshake negotiation within Qualcomm Snapdragon chipset firmware allows potentially malicious or malformed SSL/TLS handshake messages to be accepted, which could enable man-in-the-middle attacks or bypass SSL protections entirely.

MitigationApply Android security patch level from 2018-04-05 or later, which contains the vendor fix for Qualcomm SSL library input validation. Devices running earlier patch levels remain vulnerable.

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
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
Mdm9655 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 modem chipset model
    Check the device specifications or use AT commands (e.g., AT+CGMM or AT+GMM) to query the modem model. Look for model numbers Mdm9206, Mdm9607, Mdm9615, Mdm9625, Mdm9635m, Mdm9640, Mdm9645, or Mdm9655.
    Affected if The modem model matches one of the listed affected Mdm* variants.
  2. Determine the installed modem firmware version
    Query the modem firmware version using AT commands such as AT+CGMR or through the device's system information settings. The specific command may vary by device manufacturer.
    Affected if The modem firmware version falls within the affected product list (all versions of the listed Mdm* firmwares).
  3. Verify the Android security patch level
    On Android devices, go to Settings > About Phone > Build Number, or run 'getprop ro.build.version.security_patch' via ADB to check the installed security patch level.
    Affected if The security patch level is earlier than 2018-04-05, indicating the device has not received the vendor fix.
  4. Confirm SSL/TLS handshake handling
    If you have access to network logs or can perform a TLS handshake test, inspect whether the modem SSL library accepts malformed or unexpected handshake messages. This typically requires advanced debugging or penetration testing tools.
    Affected if The device accepts SSL/TLS handshake messages that deviate from RFC specifications without rejecting them.

A device is affected if it contains any of the listed Qualcomm modem firmware models (Mdm9206, Mdm9607, Mdm9615, Mdm9625, Mdm9635m, Mdm9640, Mdm9645, Mdm9655) and has not received the Android security patch level from 2018-04-05 or later.

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 Android security patch level from 2018-04-05 or later, which contains the vendor fix for Qualcomm SSL library input validation. Devices running earlier patch levels remain vulnerable.

Fix this in Mdm9206 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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