dbcve.org
Mdm9206 FirmwareOperating system · Qualcomm

CVE-2017-18129

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 and Snapdragon Mobile MDM9206, MDM9607, SD 845, MSM8996, MSM8998, it is possible for IPA (internet protocol accelerator) channels owned by one security domain to be controlled from other domains.

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 privilege escalation vulnerability in Qualcomm Snapdragon processors (MDM9206, MDM9607, SD 845, MSM8996, MSM8998) allows IPA (Internet Protocol Accelerator) channels owned by one security domain to be controlled from other domains. This isolation bypass in the IPA subsystem could allow an attacker to manipulate network traffic processing at the firmware level.

MitigationApply Android security patch level 2018-04-05 or later to affected devices, which includes the fix for this IPA isolation bypass. Contact the device OEM for firmware updates if not already 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
Mdm9206 FirmwareOperating system
Affected:all versions
Mdm9607 FirmwareOperating system
Affected:all versions
Msm8996 FirmwareOperating system
Affected:all versions
Msm8998 FirmwareOperating system
Affected:all versions
Sd 845 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 Snapdragon chipset model
    Check the processor information via 'adb shell getprop ro.hardware' or by reading /proc/cpuinfo on the device. Look for identifiers such as mdm9206, mdm9607, msm8996, msm8998, or sdm845.
    Affected if The chipset model matches one of: MDM9206, MDM9607, MSM8996, MSM8998, or SD 845.
  2. Verify the Android security patch level
    Run 'adb shell getprop ro.build.version.security_patch' or check Settings > About Phone > Android security patch level on the device.
    Affected if The security patch level is earlier than 2018-04-05, or the property returns empty or an older date.
  3. Confirm the baseband firmware version
    Run 'adb shell getprop gsm.version.baseband' to retrieve the baseband/MMODEM firmware version string.
    Affected if The returned version is present and corresponds to the affected chipset models listed, with no corresponding patch applied.
  4. Check for IPA subsystem status
    Inspect if the IPA (Internet Protocol Accelerator) driver is loaded by running 'adb shell ls /dev/ipa' or checking 'adb shell cat /proc/modules | grep ipa'.
    Affected if The IPA driver is active on a vulnerable chipset with an unpatched security level.

A device is affected if it uses any of the listed Qualcomm Snapdragon chipsets (MDM9206, MDM9607, MSM8996, MSM8998, SD 845) and has an Android security patch level earlier than 2018-04-05.

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, which includes the fix for this IPA isolation bypass. Contact the device OEM for firmware updates if not already available.

Recommended fix High confidence

Android Security Patch Level 2018-04-05 or later

  1. 1. Identify the device model and confirm it uses one of the affected Qualcomm Snapdragon chipsets (MDM9206, MDM9607, MSM8996, MSM8998, or SD 845)
  2. 2. Check the current Android security patch level on the device (Settings > About Phone > Security Patch Level)
  3. 3. If the security patch level is earlier than April 5, 2018, contact the device manufacturer for the availability of the April 2018 Android security update
  4. 4. Apply the Android security update once available from the device manufacturer
Caveat Users should ensure their device manufacturer has released the update for their specific model; not all devices may receive this patch

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

Fix this in Mdm9206 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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