dbcve.org
Mdm9607 FirmwareOperating system · Qualcomm

CVE-2018-11888

HIGH · 7.8 CVSS v3.0 Published 2019-02-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
Unauthorized access may be allowed by the SCP11 Crypto Services TA will processing commands from other TA in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile and Snapdragon Voice & Music in versions MDM9607, MDM9650, MDM9655, MSM8996AU, SD 210/SD 212/SD 205, SD 410/12, SD 425, SD 427, SD 430, SD 435, SD 439 / SD 429, SD 450, SD 615/16/SD 415, SD 625, SD 632, SD 650/52, SD 820, SD 820A, SD 835, SD 8CX, SDM439, Snapdragon_High_Med_2016.

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

The SCP11 Crypto Services Trusted Application (TA) in Qualcomm Snapdragon processors contains an access control vulnerability where it improperly processes commands from other TAs. This allows unauthorized access to cryptographic services within the Trusted Execution Environment (TEE), potentially enabling privilege escalation between TAs.

MitigationApply vendor-supplied firmware patches from Qualcomm/device manufacturers. This is a TEE/TA firmware issue requiring updated SecureOS binaries.

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
Sd 210 FirmwareOperating system
Affected:all versions
Sd 212 FirmwareOperating system
Affected:all versions
Sd 205 FirmwareOperating system
Affected:all versions
Sd 410 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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:L/PR:L/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
    Check the device specifications or system-on-chip (SoC) information to determine if the device uses one of the affected Qualcomm Snapdragon variants: Mdm9607, Mdm9650, Mdm9655, Msm8996au,Sd 210, Sd 212, Sd 205, or Sd 410.
    Affected if The device does not use one of these chipsets, then it is not affected by this specific CVE.
  2. Check baseband processor firmware version
    Access the device's baseband or modem firmware information through engineering diagnostic modes, manufacturer service menus, or by querying AT commands (if available): at+ver or at+cgmr to retrieve CP firmware version.
    Affected if The baseband firmware version cannot be determined or verified as patched, the device may still be vulnerable.
  3. Verify TEE and TA configuration
    If you have access to the Trusted Execution Environment (TEE) diagnostic interfaces, query the installed Trusted Applications (TAs) and verify the SCP11 Crypto Services TA version and its command processing permissions.
    Affected if The SCP11 Crypto Services TA accepts commands from unauthorized TAs or shows no access control enforcement between TAs.
  4. Check SecureOS version
    If accessible through secure debug or manufacturer diagnostic tools, retrieve the SecureOS firmware version associated with the TEE implementation.
    Affected if The SecureOS version matches an unpatched release for the affected chipset.

The device is affected if it uses one of the listed Qualcomm Snapdragon chipsets (Mdm9607, Mdm9650, Mdm9655, Msm8996au, Sd 210, Sd 212, Sd 205, Sd 410) and the firmware has not been updated with the vendor-supplied security patch.

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

Apply vendor-supplied firmware patches from Qualcomm/device manufacturers. This is a TEE/TA firmware issue requiring updated SecureOS binaries.

Fix this in Mdm9607 Firmware Scoped from the published advisory
  • Consultation16.0 h
  • Implementation40.0 h
  • Testing24.0 h
  • Review / QA12.0 h
92.0 hours of engineering $16,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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