dbcve.org
Mdm9206 FirmwareOperating system · Qualcomm

CVE-2017-18132

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, MDM8996, an out-of-bounds access can potentially occur in tz_assign().

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

Out-of-bounds memory access in tz_assign() function within Qualcomm's TrustZone (trusted execution environment) on Snapdragon MDM9206, MDM9607, and MDM8996 chips. This memory corruption vulnerability in secure world firmware allows potential privilege escalation or code execution with the highest privileges, enabling complete device compromise.

MitigationApply Android security patch level 2018-04-05 or later, which includes the vendor-specific fix for the TrustZone vulnerability. Devices running older patch levels should be prioritized for update or replacement.

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

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. Verify Android Security Patch Level
    Run 'getprop ro.build.version.security_patch' or check Settings > About Phone > Android Security Patch Level
    Affected if The patch level is earlier than 2018-04-05 or not set, indicating the vulnerability is not patched
  2. Confirm device model is affected
    Check the device model via 'getprop ro.product.device' or 'getprop ro.product.name' and verify it uses one of the affected Qualcomm chipsets: MDM9206, MDM9606, or MDM8996
    Affected if The device is built on MDM9206, MDM9607, or MSM8996 chipset and the security patch level is pre-April 2018
  3. Check TrustZone version if accessible
    Some devices expose TrustZone info via 'getprop ro.trustzone.version' or by reading /sys/class/misc/tee/version if available
    Affected if The TrustZone version is present but cannot be verified as patched, or no version info is accessible on an affected chipset
  4. Check baseband/modem firmware version
    Run 'getprop gsm.version.baseband' or check Settings > About Phone > Baseband version to identify the modem firmware
    Affected if The baseband firmware is from an older build on an affected chipset without confirmed patch level

A device is likely affected if it uses an MDM9206, MDM9607, or MSM8996 chipset and its Android Security Patch Level predates April 5, 2018, or is unknown.

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 includes the vendor-specific fix for the TrustZone vulnerability. Devices running older patch levels should be prioritized for update or replacement.

Recommended fix High confidence

Android devices with security patch level 2018-04-05 or later (e.g., Android 8.0, 8.1, 9.0 with April 2018 security update)

  1. 1. Check if your Android device receives the monthly security update patch level 2018-04-05 or later
  2. 2. Go to Settings > About Phone > Software Update on your device
  3. 3. Check the Android security patch level under Settings > About Phone > Android security patch level
  4. 4. If the security patch level is earlier than 2018-04-05, contact your device manufacturer for firmware update availability
  5. 5. Apply the latest available Android security update from your device manufacturer
  6. 6. Verify after update that the Android security patch level shows 2018-04-05 or later
Caveat Device must still be supported by manufacturer for security updates; older devices may not receive patches

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

Fix this in Mdm9206 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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