dbcve.org
Ipq8074 FirmwareOperating system · Qualcomm

CVE-2018-13908

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
Truncated access authentication token leads to weakened access control for stored secure application data in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking in IPQ8074, MDM9150, MDM9206, MDM9607, MDM9650, MDM9655, MSM8909W, MSM8996AU, QCA8081, QCS405, QCS605, Qualcomm 215, 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 636, SD 650/52, SD 712 / SD 710 / SD 670, SD 820, SD 820A, SD 835, SD 845 / SD 850, SD 8CX, SDA660, SDM439, SDM630, SDM660, Snapdragon_High_Med_2016, SXR1130

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 vulnerability in Qualcomm Snapdragon chipsets allows truncated access authentication tokens to weaken access controls for stored secure application data. The authentication token truncation reduces the effective key space, potentially allowing unauthorized access to sensitive application data stored on affected devices.

MitigationThis vulnerability requires a firmware update from Qualcomm that corrects token handling. Downstream device manufacturers must integrate and distribute this patch to end users. Users should apply available security updates from their device manufacturers.

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
Mdm9150 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
Msm8909w FirmwareOperating system
Affected:all versions
Msm8996au 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 chipset model
    Check your device specifications, system information, or bootloader/boot messages to determine the exact Qualcomm Snapdragon chipset model (e.g., Ipq8074, Mdm9150, Mdm9206, Mdm9607, Mdm9650, Mdm9655, Msm8909w, Msm8996au)
    Affected if The identified chipset matches any of the following: Ipq8074, Mdm9150, Mdm9206, Mdm9607, Mdm9650, Mdm9655, Msm8909w, or Msm8996au
  2. Confirm the device uses one of the affected Snapdragon variants
    Review the device hardware documentation, FCC filings, or teardown information to verify the specific Qualcomm chipset variant in use
    Affected if The device employs any of the listed affected Qualcomm chipset models
  3. Check firmware or baseband version
    Access the device's about page, system settings, or diagnostic interface (e.g., *#06# on mobile, or administrative console for networking gear) to retrieve the current firmware/baseband version string
    Affected if The firmware version cannot be verified as patched, or the device runs the original vendor firmware with all versions of the affected chipset
  4. Verify secure application data access behavior
    If you develop or test applications that use Qualcomm's secure execution environment (SEE) or Trusted Execution Environment (TEE), examine whether authentication token length validation is properly enforced when accessing protected storage
    Affected if Authentication tokens appear truncated or the key space is reduced when accessing secure application data stored by the chipset

The device is affected if it contains any of the following Qualcomm chipsets: Ipq8074, Mdm9150, Mdm9206, Mdm9607, Mdm9650, Mdm9655, Msm8909w, or Msm8996au, and the firmware has not been updated to address the token truncation vulnerability.

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

This vulnerability requires a firmware update from Qualcomm that corrects token handling. Downstream device manufacturers must integrate and distribute this patch to end users. Users should apply available security updates from their device manufacturers.

Fix this in Ipq8074 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation40.0 h
  • Testing24.0 h
  • Review / QA16.0 h
88.0 hours of engineering $15,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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