dbcve.org
Mdm9206 FirmwareOperating system · Qualcomm

CVE-2017-18130

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 Automobile, Snapdragon Mobile, and Snapdragon Wear MDM9206, MDM9607, MDM9650, SD 210/SD 212/SD 205, SD 400, SD 425, SD 430, SD 450, SD 615/16/SD 415, SD 617, SD 625, SD 650/52, SD 808, SD 820, SD 820A, SD 835, SD 845, while playing an ASF file, a buffer over-read can potentially 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

A buffer over-read vulnerability exists in Qualcomm Snapdragon chipset firmware when parsing ASF (Advanced Systems Format) media files. This memory safety issue in the media parsing code can allow remote code execution or information disclosure without authentication, given the CVSS 9.8 critical rating.

MitigationApply Android security patch level 2018-04-05 or later, which contains the Qualcomm fix for this vulnerability. Users should ensure their device manufacturers have backported the fix to supported device models.

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
Mdm9650 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 400 FirmwareOperating system
Affected:all versions
Sd 425 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 Qualcomm chipset model
    Check the device hardware information via /proc/cpuinfo, or use commands like 'lshw' or check 'Settings > About Phone' to determine the exact chipset (e.g., Mdm9206, Mdm9607, Mdm9650, Sd 210, Sd 212, Sd 205, Sd 400, Sd 425)
    Affected if The chipset matches any of the affected models: Mdm9206, Mdm9607, Mdm9650, Sd 210, Sd 212, Sd 205, Sd 400, or Sd 425
  2. Verify the Android security patch level
    Check 'Settings > About Phone > Android security patch level' or run 'getprop ro.build.version.security_patch' to see the installed patch date
    Affected if The patch level is earlier than 2018-04-05, meaning the fix has not been applied
  3. Confirm firmware version of the affected chipset
    Check the baseband or modem firmware version via 'getprop | grep -i version' or 'AT+CGMR' command (if modem AT interface is accessible), then compare against the affected product list
    Affected if The firmware version corresponds to any of the listed affected products (Mdm9206, Mdm9607, Mdm9650, Sd 210, Sd 212, Sd 205, Sd 400, Sd 425) with no patch applied
  4. Determine if ASF media parsing is in use
    Monitor or audit media player usage and file processing. Check if the device or application processes ASF (Advanced Systems Format) media files, as this is the attack vector for the vulnerability
    Affected if ASF media files are being parsed by the device media framework, which triggers the vulnerable parsing code path

The device is affected if it uses any of the listed Qualcomm chipsets (Mdm9206, Mdm9607, Mdm9650, Sd 210, Sd 212, Sd 205, Sd 400, Sd 425) AND has an Android security patch level earlier than 2018-04-05, and processes ASF media files.

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, which contains the Qualcomm fix for this vulnerability. Users should ensure their device manufacturers have backported the fix to supported device models.

Recommended fix High confidence

Android devices with security patch level 2018-04-05 or later

  1. Check the current Android security patch level on the device (Settings > About Phone > Security patch level)
  2. Apply the Android security update for April 2018 or later, which contains the fix for this vulnerability
  3. If the device manufacturer has not released an update with the April 2018 security patch level, contact the device manufacturer for support
  4. Consider upgrading to a device that receives regular security updates if the current device is no longer supported
Caveat The fix is delivered via monthly Android security updates; older devices may not receive patches if manufacturer support has ended

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

Fix this in Mdm9206 Firmware Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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