dbcve.org
Mdm9206 FirmwareOperating system · Qualcomm

CVE-2018-11999

MEDIUM · 5.5 CVSS v3.0 Published 2019-01-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
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
Improper input validation in trustzone can lead to denial of service in snapdragon automobile, snapdragon mobile and snapdragon wear in versions MDM9206, MDM9607, MDM9635M, MDM9650, MDM9655, MSM8996AU, SD 210/SD 212/SD 205, SD 410/12, SD 636, SD 820, SD 820A, SD 835, SD 845 / SD 850, SDA660, SDM630, SDM660, SDX24

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

Improper input validation in the TrustZone secure execution environment of Qualcomm Snapdragon processors allows an attacker to cause a denial of service. TrustZone is a hardware-based security subsystem that separates sensitive operations from the main OS; the vulnerability enables a DoS condition within the Trusted Execution Environment.

MitigationApply vendor-supplied firmware/security updates from Qualcomm and device OEMs for affected Snapdragon chipsets. Organizations should inventory affected devices and deploy updates through their device management infrastructure.

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
Mdm9635m 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

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
None
Integrity
None
Availability
High

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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
    On Android devices, check /proc/cpuinfo or use 'getprop' command to retrieve the hardware/crypto processor information. For IoT or embedded devices, consult the device documentation or BOM (Bill of Materials).
    Affected if The chipset model matches any of the following: Mdm9206, Mdm9607, Mdm9635m, Mdm9650, Mdm9655, Msm8996au, Sd 210, or Sd 212
  2. Verify the processor is a Snapdragon variant
    Confirm the identified chipset belongs to the Qualcomm Snapdragon product line. The affected models are Snapdragon-based modem and processorfirmware.
    Affected if The device uses a Qualcomm Snapdragon chipset listed in the affected products
  3. Confirm TrustZone is present
    TrustZone is a hardware-based security feature built into these Snapdragon processors. Verify the device has a TrustZone-enabled Secure Execution Environment. This is typically visible in boot logs, security certifications, or by checking for TEE (Trusted Execution Environment) drivers in /dev or /sys.
    Affected if The device implements TrustZone (the vulnerability exists within the TrustZone secure environment)
  4. Check firmware version for context
    While all versions are affected per the advisory, note the current firmware version for inventory purposes. On Android: 'getprop' or check under Settings > About Phone > Kernel version or Baseband version.
    Affected if Any firmware version is installed on an affected chipset - all versions are vulnerable

If the device uses any of the listed Qualcomm Snapdragon chipsets (Mdm9206, Mdm9607, Mdm9635m, Mdm9650, Mdm9655, Msm8996au, Sd 210, Sd 212) and implements TrustZone, the environment is affected by this CVE.

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/security updates from Qualcomm and device OEMs for affected Snapdragon chipsets. Organizations should inventory affected devices and deploy updates through their device management infrastructure.

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-2018-11999 — 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-11999 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