dbcve.org
Msm8996 FirmwareOperating system · Qualcomm

CVE-2014-10050

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 Mobile MSM8996, MSM8939, MSM8976, MSM8917, SDM845, and SDM660, access control collision vulnerability when accessing the replay protected memory block.

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

Access control collision vulnerability in the Replay Protected Memory Block (RPMB) partition of specific Qualcomm Snapdragon processors (MSM8996, MSM8939, MSM8976, MSM8917, SDM845, SDM660). RPMB is a hardware-secured storage area typically used for sensitive data like DRM keys and secure boot credentials; the collision allows potential unauthorized access to this protected memory region.

MitigationApply vendor-supplied firmware/BIOS updates delivered through Android security patch levels dated 2018-04-05 or later for affected devices. No user-configurable mitigation available; this is a hardware/firmware-level access control flaw requiring vendor patch deployment.

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
Msm8996 FirmwareOperating system
Affected:all versions
Msm8939 FirmwareOperating system
Affected:all versions
Msm8976 FirmwareOperating system
Affected:all versions
Msm8917 FirmwareOperating system
Affected:all versions
Sdm845 FirmwareOperating system
Affected:all versions
Sdm660 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 Snapdragon SoC model
    Check the processor model via /proc/cpuinfo, or use 'getprop ro.board.platform' or 'getprop ro.hardware' on Android devices
    Affected if The model number matches one of: MSM8996, MSM8939, MSM8976, MSM8917, SDM845, or SDM660
  2. Verify RPMB partition accessibility
    Check if the RPMB partition exists and is accessible on the device by examining /dev/block/*/rpmb or using 'ls -la /dev/rpmb*'
    Affected if RPMB device node exists and shows read/write access without proper authentication constraints
  3. Check Android security patch level
    Run 'getprop ro.build.version.security_patch' to retrieve the installed Android security patch date
    Affected if The patch level is earlier than 2018-04-05 or is not set, indicating the vendor firmware update has not been applied
  4. Confirm firmware version
    Query the baseband or modem firmware version via 'getprop gsm.version.baseband' or check the bootloader version via 'getprop ro.bootloader'
    Affected if The firmware version is present and corresponds to the affected Snapdragon variants listed, regardless of specific version number since all versions are vulnerable

The device is affected if it contains any of the listed Snapdragon processors (MSM8996, MSM8939, MSM8976, MSM8917, SDM845, SDM660) and the Android security patch level is earlier than 2018-04-05 or the vendor firmware update has not been applied.

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 vendor-supplied firmware/BIOS updates delivered through Android security patch levels dated 2018-04-05 or later for affected devices. No user-configurable mitigation available; this is a hardware/firmware-level access control flaw requiring vendor patch deployment.

Recommended fix Moderate confidence

Android devices with security patch level 2018-04-05 or later containing the Qualcomm firmware fix

  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 2018-04-05, apply the latest available Android system update from your device manufacturer
  3. Verify after update that the security patch level shows 2018-04-05 or later
  4. For enterprise/embedded deployments, contact the device OEM for firmware-level updates if OTA updates are unavailable
Caveat Minimal; security patches typically do not introduce breaking changes but may require device reboot

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

Fix this in Msm8996 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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