dbcve.org
Mdm9206 FirmwareOperating system · Qualcomm

CVE-2017-18131

HIGH · 7.8 CVSS v3.0 Published 2019-05-06
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
In QTEE, an incorrect fuse value can be blown in Snapdragon Automobile, Snapdragon Mobile, Snapdragon Wear in version MDM9206, MDM9607, MSM8996AU, SD 210/SD 212/SD 205, SD 410/12, SD 425, SD 427, SD 430, SD 435, SD 450, SD 615/16/SD 415, SD 625, SD 820, SD 820A, SD 835, SD 845, SDM429, SDM439, SDM630, SDM632, SDM636, SDM660, 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

This vulnerability in Qualcomm's Trusted Execution Environment (QTEE) allows an incorrect fuse value to be blown, potentially misconfiguring security settings in the hardware. The e-fuse mechanism stores critical security parameters, and an incorrectly blown fuse could compromise the trusted computing base of affected Snapdragon chipsets.

MitigationApply firmware updates provided by device OEMs or chipset vendors; this requires patching at the hardware/firmware level to correct the QTEE fuse configuration.

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
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
Sd 412 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
    On Android devices, check /proc/cpuinfo or use 'getprop' commands (getprop ro.hardware, getprop ro.board.platform) to identify the chipset. On embedded devices, check device tree or bootloader information.
    Affected if The chipset matches one of the following: Mdm9206, Mdm9607, Msm8996au, Sd 210, Sd 212, Sd 205, Sd 410, or Sd 412.
  2. Verify QTEE is present
    Check system logs or debug information for QTEE (Qualcomm Trusted Execution Environment) initialization messages. Look for 'QTEE', 'tee', or 'trusted execution' in dmesg, logcat, or /proc/tee_info if available.
    Affected if QTEE is present and initialized on the device.
  3. Confirm firmware version
    Query the firmware version through device properties (getprop ro.build.id, getprop ro qualcomm firmware version) or check baseband version via AT commands or /proc/version.
    Affected if The device runs any firmware version on the affected chipsets (all versions are affected per the CVE).
  4. Inspect e-fuse configuration
    Access e-fuse registers through vendor-specific diagnostic tools or debug interfaces (such as Sahara/FIREHOPE protocols used by Qualcomm). If available, check /sys/class/fuse or vendor-specific debugfs entries. This typically requires root access and Qualcomm debugging tools.
    Affected if The e-fuse values for security configuration are found to be incorrectly blown or set to non-default values that weaken security settings.

A user is affected if their device uses one of the listed Qualcomm chipsets (Mdm9206, Mdm9607, Msm8996au, Sd 210/212/205/410/412) and has an incorrectly configured e-fuse setting that compromises QTEE security, which requires vendor-specific tools to inspect.

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 firmware updates provided by device OEMs or chipset vendors; this requires patching at the hardware/firmware level to correct the QTEE fuse configuration.

Fix this in Mdm9206 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation40.0 h
  • Testing24.0 h
  • Review / QA12.0 h
84.0 hours of engineering $14,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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