dbcve.org
Mdm9206 FirmwareOperating system · Qualcomm

CVE-2017-11011

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 and Snapdragon Wear MDM9206, MDM9607, SD 210/SD 212/SD 205, SD 425, SD 430, SD 450, SD 625, SD 820, SD 835, a Use After Free condition can occur in a communication API.

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 Use After Free memory corruption vulnerability in the communication API of Qualcomm Snapdragon chipsets (MDM9206, MDM9607, SD 210/212/205, SD 425, SD 430, SD 450, SD 625, SD 820, SD 835) allows remote attackers to potentially execute arbitrary code or cause denial of service via crafted input.

MitigationApply Android security patch level 2018-04-05 or later to affected devices, or obtain and deploy OEM-provided firmware updates containing the Qualcomm fix.

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
Sd 210 FirmwareOperating system
Affected:all versions
Sd 212 FirmwareOperating system
Affected:all versions
Sd 205 FirmwareOperating system
Affected:all versions
Sd 425 FirmwareOperating system
Affected:all versions
Sd 430 FirmwareOperating system
Affected:all versions
Sd 450 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 chipset model
    Run 'getprop ro.board.platform' or check /proc/cpuinfo to find the Qualcomm Snapdragon model number
    Affected if The chipset matches MDM9206, MDM9607, SD 210, SD 212, SD 205, SD 425, SD 430, SD 450, SD 625, SD 820, or SD 835
  2. Check baseband firmware version
    Run 'getprop gsm.version.baseband' to retrieve the modem/baseband firmware version
    Affected if The firmware version is present and matches the affected chipset models (all versions are vulnerable)
  3. Verify communication API availability
    Check if the device communication services are active by examining running processes related to telephony or radio (e.g., 'ps -A | grep -i ril' or 'dumpsys telephony')
    Affected if The RIL (Radio Interface Layer) or communication API services are running and accessible

A device is affected if it uses any of the listed Qualcomm Snapdragon chipsets (MDM9206, MDM9607, SD 210/212/205/425/430/450/625/820/835) and has active communication services, as the Use After Free vulnerability exists in the communication API of these chipsets across all firmware versions.

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, or obtain and deploy OEM-provided firmware updates containing the Qualcomm fix.

Recommended fix High confidence

Android Security Patch Level 2018-04-05 or later (contact OEM for device-specific update)

  1. Check the current Android security patch level on the device by going to Settings > About Phone > Security Patch Level
  2. Contact the device manufacturer (OEM) to obtain and apply the Android security patch level 2018-04-05 or later for the specific Snapdragon chipset型号
  3. After receiving the update from the OEM, install the security update through Settings > System > Software Update
  4. Verify the security patch was successfully applied by confirming the Security Patch Level shows April 2018 or later in Settings > About Phone > Security Patch Level

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

Fix this in Mdm9206 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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