dbcve.org
AndroidOperating system · Google

CVE-2017-14906

CRITICAL · 9.8 CVSS v3.0 Published 2018-03-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 Android before 2018-01-05 on Qualcomm Snapdragon IoT, Snapdragon Mobile MDM9206, MDM9607, MSM8909W, SD 210/SD 212/SD 205, SD 410/12, PKCS7 padding is not supported by the crypto storage APIs.

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

The crypto storage APIs on affected Qualcomm Snapdragon IoT and mobile chipsets (MDM9206, MDM9607, MSM8909W, SD 210/212/205, SD 410/12) lack support for PKCS7 padding, a standard block cipher padding scheme. This omission can cause decryption failures, interoperability issues with properly-padded data, and potential data exposure or corruption when standard padding is expected.

MitigationApply Qualcomm firmware updates and Android security patches released after 2018-01-05 that add PKCS7 padding support to the crypto storage APIs; for unsupported devices, consider network segmentation and avoid storing sensitive data using affected cryptographic functions.

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
AndroidOperating 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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/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 /proc/cpuinfo or use 'getprop' commands (e.g., 'getprop ro.board.platform', 'getprop ro.product.device') to retrieve the chipset or device model identifier
    Affected if The chipset model matches one of the affected variants: MDM9206, MDM9607, MSM8909W, SD 210, SD 212, SD 205, SD 410, or SD 412
  2. Confirm Android version
    Run 'getprop ro.build.version.release' to check the Android OS version
    Affected if Android version is any version (the summary indicates all versions are affected)
  3. Determine if crypto storage APIs are in use
    Review application code or system configuration to identify if data encryption/decryption is performed using the device's hardware crypto storage APIs (such as those in the Secure File Storage or Keymaster components)
    Affected if The device uses hardware-backed crypto storage functions for encrypting or decrypting stored data, particularly for file-based or block-level encryption
  4. Verify firmware age
    Check if the device firmware and Android security patches predate the 2018-01-05 mitigation release using 'getprop ro.build.version.security.patch'
    Affected if The security patch level is earlier than January 2018, indicating the PKCS7 padding support may not yet be implemented

The device is affected if it contains one of the listed Qualcomm chipsets (MDM9206, MDM9607, MSM8909W, SD 210/212/205, SD 410/12) and uses hardware crypto storage APIs for data encryption, especially if the firmware predates the January 2018 patches.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Qualcomm firmware updates and Android security patches released after 2018-01-05 that add PKCS7 padding support to the crypto storage APIs; for unsupported devices, consider network segmentation and avoid storing sensitive data using affected cryptographic functions.

Recommended fix Moderate confidence

Android with January 5, 2018 security patch level or later (2018-01-05)

  1. 1. Identify if the affected device uses one of the vulnerable Qualcomm Snapdragon components: MDM9206, MDM9607, MSM8909W, SD 210/SD 212/SD 205, or SD 410/12.
  2. 2. Check the current Android security patch level on the device (Settings > About Phone > Android security patch level).
  3. 3. If the patch level is earlier than January 5, 2018, check with the device OEM for available firmware updates containing the January 2018 Android Security Bulletin fixes.
  4. 4. Apply the OEM-provided system update that includes the January 2018 security patch level or later.
Caveat Some older devices may no longer receive security updates from OEMs; consider device replacement if update is unavailable

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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