dbcve.org
Mdm9206 FirmwareOperating system · Qualcomm

CVE-2014-10053

CRITICAL · 9.8 CVSS v3.0 Published 2018-04-18
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-04-05 or earlier security patch level on Qualcomm Snapdragon Automobile, Snapdragon Mobile, and Snapdragon Wear MDM9206, MDM9650, MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 425, SD 430, SD 615/16/SD 415, SD 450, SD 617, SD 625, SD 650/52, SD 800, SD 808, SD 810, SD 820, SD 820A, SD 835, SD 845, and SD 850, data access is not properly validated in the Widevine secure application.

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

This vulnerability in Qualcomm Snapdragon processors allows improper data access validation in the Widevine secure application (DRM component). The lack of proper input validation could enable unauthorized access to protected content or sensitive data processed by the Widevine secure media subsystem.

MitigationApply the April 2018 or later Android security patch level to affected devices. Organizations should identify all vulnerable Qualcomm-based devices in their environment and ensure they receive vendor-provided firmware updates through their OEM/carrier channels.

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
Sd 820a FirmwareOperating system
Affected:all versions
Mdm9650 FirmwareOperating system
Affected:all versions
Msm8909w 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 400 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
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 processor model
    Retrieve the processor identifier using Android system properties (e.g., getprop ro.hardware or getprop ro.board.platform) or check device specifications from the OEM
    Affected if The processor model matches any of the following: Mdm9206, Sd 820a, Mdm9650, Msm8909w, Sd 210, Sd 212, Sd 205, or Sd 400
  2. Confirm Widevine DRM is in use
    Check if the device uses Widevine for DRM-protected content playback by inspecting DRM configuration files or media player settings
    Affected if Widevine secure media subsystem is enabled and processing protected content on the device
  3. Verify the firmware version
    Check the installed firmware version via build information (e.g., getprop ro.build.version.firmware) or OEM-provided device details
    Affected if The firmware version corresponds to any version of the affected Qualcomm products listed (all versions are impacted)
  4. Check the Android security patch level
    Verify the installed Android security patch level in Settings > About Phone > Android security patch level, or via command: getprop ro.build.version.security_patch
    Affected if The security patch level is dated before April 2018

A user is affected if the device contains a listed Qualcomm processor with Widevine DRM enabled and has a security patch level earlier than April 2018.

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 the April 2018 or later Android security patch level to affected devices. Organizations should identify all vulnerable Qualcomm-based devices in their environment and ensure they receive vendor-provided firmware updates through their OEM/carrier channels.

Recommended fix High confidence

Android security patch level 2018-04-05 or later (or the latest available security update from the device manufacturer)

  1. Check the current Android security patch level on the device (Settings > About Phone > Security patch level)
  2. If the security patch level is earlier than April 5, 2018, apply the latest available Android security update from the device manufacturer
  3. Ensure the device receives Android security patch level 2018-04-05 or later to address the Widevine improper access control vulnerability
Caveat Security updates typically do not introduce breaking changes; however, ensure backup of data before applying updates

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

Fix this in Mdm9206 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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