dbcve.org
Ipq8074 FirmwareOperating system · Qualcomm

CVE-2018-13910

HIGH · 7.8 CVSS v3.0 Published 2019-06-14
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
Out-of-Bounds access in TZ due to invalid index calculated to check against DDR in Snapdragon Auto, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking in IPQ8074, MDM9206, MDM9607, MDM9650, MDM9655, MSM8996AU, QCA8081, Qualcomm 215, SD 410/12, SD 425, SD 427, SD 430, SD 435, SD 439 / SD 429, SD 450, SD 625, SD 632, SD 650/52, SD 820, SD 820A, 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 · high confidence

An out-of-bounds access vulnerability exists in the TrustZone (TZ) secure component of Qualcomm Snapdragon processors due to an invalid index calculation used when checking memory addresses against DDR. This allows a non-secure world attacker to potentially access secure memory regions, enabling privilege escalation to the TrustZone secure environment.

MitigationApply vendor-supplied firmware/patch from Qualcomm that corrects the invalid index calculation in TrustZone memory boundary checks. This is a firmware-level fix requiring OEM/ODM distribution.

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
Ipq8074 FirmwareOperating system
Affected:all versions
Mdm9206 FirmwareOperating system
Affected:all versions
Mdm9607 FirmwareOperating system
Affected:all versions
Mdm9650 FirmwareOperating system
Affected:all versions
Mdm9655 FirmwareOperating system
Affected:all versions
Msm8996au FirmwareOperating system
Affected:all versions
Qca8081 FirmwareOperating system
Affected:all versions
Qm215 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 Qualcomm processor model in the device
    Check the device specifications, hardware inventory, or boot logs for the Snapdragon/Qualcomm processor model number (e.g., Ipq8074, Mdm9206, Mdm9607, Mdm9650, Mdm9655, Msm8996au, Qca8081, Qm215)
    Affected if The device uses any of the following processors: Ipq8074, Mdm9206, Mdm9607, Mdm9650, Mdm9655, Msm8996au, Qca8081, or Qm215
  2. Verify TrustZone is enabled on the system
    Check if the device implements ARM TrustZone technology by examining boot logs, security configurations, or system files for TZ, TEE, or secure world indicators
    Affected if TrustZone is present and the processor is one of the affected models listed above
  3. Confirm the device firmware is from an affected version range
    Since all versions of the listed firmware are affected, check the installed firmware version against the list of affected products to confirm it matches any of: Ipq8074 Firmware, Mdm9206 Firmware, Mdm9607 Firmware, Mdm9650 Firmware, Mdm9655 Firmware, Msm8996au Firmware, Qca8081 Firmware, or Qm215 Firmware
    Affected if The firmware version corresponds to any of the affected products and the TrustZone memory boundary check is in use

A device is affected if it contains any of the listed Qualcomm Snapdragon processors (Ipq8074, Mdm9206, Mdm9607, Mdm9650, Mdm9655, Msm8996au, Qca8081, Qm215) and runs the associated firmware with TrustZone enabled.

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/patch from Qualcomm that corrects the invalid index calculation in TrustZone memory boundary checks. This is a firmware-level fix requiring OEM/ODM distribution.

Fix this in Ipq8074 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-13910 — 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-13910 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