dbcve.org
Mdm9206 FirmwareOperating system · Qualcomm

CVE-2017-8276

HIGH · 7.8 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 →
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
Improper authorization involving a fuse in TrustZone in snapdragon automobile, snapdragon mobile and snapdragon wear in versions MDM9206, MDM9607, 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 636, SD 650/52, SD 810, SD 820, SD 820A, SD 835, SDA660, SDM439, SDM630, SDM660, SDX24, 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 involves improper authorization checks for eFuse access within Qualcomm's TrustZone secure execution environment. TrustZone creates a 'secure world' for sensitive operations, and eFuses are one-time programmable memory cells storing encryption keys and security configurations. The improper authorization could allow bypass of security controls, potentially enabling access to sensitive cryptographic material or modification of security settings.

MitigationApply vendor-supplied firmware patches from Qualcomm and device OEMs. Since this is a hardware/firmware-level issue in TrustZone, users must obtain and install firmware updates from their device manufacturers. No workarounds exist for improper authorization in secure boot/fuse logic.

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
    Examine system information, device diagnostics, or hardware specifications to determine the exact Qualcomm chip (Mdm9206, Mdm9607, Msm8996au, SD 210, SD 212, SD 205, SD 410, or SD 412) present in the device
    Affected if The chipset matches any of the following: Mdm9206, Mdm9607, Msm8996au, Sd 210, Sd 212, Sd 205, Sd 410, or Sd 412
  2. Determine the firmware version
    Access the device's modem or system firmware version through diagnostic tools, AT commands (for modems), or system information utilities. Compare the installed firmware version against the affected product list
    Affected if The device firmware matches any of the listed affected products (all versions of Mdm9206, Mdm9607, Msm8996au, Sd 210, Sd 212, Sd 205, Sd 410, Sd 412)
  3. Verify TrustZone is enabled
    Check system security settings or boot configuration to confirm the TrustZone secure execution environment is active on the device
    Affected if TrustZone is enabled and the chipset is one of the affected models (the vulnerability exists in the TrustZone eFuse authorization logic)
  4. Inspect eFuse configuration access
    Examine security logs or diagnostic outputs for eFuse read/write operations to determine if unauthorized access patterns exist or if security controls are being bypassed
    Affected if eFuse access controls are present and the device runs on any affected Qualcomm firmware version

The device is affected if it contains any of the listed Qualcomm chipsets (Mdm9206, Mdm9607, Msm8996au, SD 210, SD 212, SD 205, SD 410, SD 412) with TrustZone and eFuse functionality enabled, as all firmware versions of these products contain the improper authorization 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

Apply vendor-supplied firmware patches from Qualcomm and device OEMs. Since this is a hardware/firmware-level issue in TrustZone, users must obtain and install firmware updates from their device manufacturers. No workarounds exist for improper authorization in secure boot/fuse logic.

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-2017-8276 — 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-8276 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