dbcve.org
Mdm9607 FirmwareOperating system · Qualcomm

CVE-2018-11935

MEDIUM · 5.3 CVSS v3.0 Published 2019-02-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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
Improper input validation might result in incorrect app id returned to the caller Instead of returning failure in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile in versions MDM9607, MDM9650, MDM9655, MSM8996AU, QCS605, SD 210/SD 212/SD 205, SD 410/12, SD 615/16/SD 415, SD 636, SD 675, SD 712 / SD 710 / SD 670, SD 820, SD 820A, SD 835, SD 845 / SD 850, SD 8CX, SDA660, SDM630, SDM660, 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 · moderate confidence

Improper input validation in multiple Qualcomm Snapdragon chipset generations (mobile, auto, compute, IoT) can cause incorrect application IDs to be returned to callers instead of proper failure responses. This affects 21 different chipset models across multiple product lines.

MitigationThis is a firmware-level vulnerability requiring patches from Qualcomm and subsequent OEM/firmware updates to affected devices. Users should apply vendor-supplied security updates when available.

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
Mdm9607 FirmwareOperating system
Affected:all versions
Mdm9650 FirmwareOperating system
Affected:all versions
Mdm9655 FirmwareOperating system
Affected:all versions
Msm8996au FirmwareOperating system
Affected:all versions
Qcs605 FirmwareOperating system
Affected:all versions
Sd 210 FirmwareOperating system
Affected:all versions
Sd 212 FirmwareOperating system
Affected:all versions
Sd 205 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
Low
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

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
    Query the device or system information to determine the exact Qualcomm Snapdragon chipset model number (e.g., Mdm9607, Mdm9650, Mdm9655, Msm8996au, Qcs605, Sd 210, Sd 212, Sd 205). This may be found in /proc/cpuinfo on Linux, system diagnostics on Android, or hardware inventory for IoT/automotive devices.
    Affected if The chipset model matches any of the following: Mdm9607, Mdm9650, Mdm9655, Msm8996au, Qcs605, Sd 210, Sd 212, or Sd 205.
  2. Verify the firmware variant
    Check the firmware version or build information associated with the identified chipset. On mobile devices, this is typically found in Settings > About Phone > Build Number or through AT commands (e.g., ATI for modem info). For IoT or automotive modules, consult the vendor documentation for firmware inspection methods.
    Affected if The firmware variant corresponds to any of the affected chipset models listed, regardless of version number.
  3. Confirm the vulnerability scope
    Since CVE-2018-11935 affects ALL versions of the listed firmware variants, cross-reference your identified chipset and firmware combination against the affected product list.
    Affected if Any device running firmware for Mdm9607, Mdm9650, Mdm9655, Msm8996au, Qcs605, Sd 210, Sd 212, or Sd 205 is affected by this vulnerability.

A device is affected if it utilizes any of the listed Qualcomm firmware variants (Mdm9607, Mdm9650, Mdm9655, Msm8996au, Qcs605, Sd 210, Sd 212, Sd 205), as all versions of these specific chipsets 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

This is a firmware-level vulnerability requiring patches from Qualcomm and subsequent OEM/firmware updates to affected devices. Users should apply vendor-supplied security updates when available.

Fix this in Mdm9607 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Testing16.0 h
  • Review / QA8.0 h
32.0 hours of engineering $5,440
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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