dbcve.org
Mdm9206 FirmwareOperating system · Qualcomm

CVE-2014-10045

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 and Snapdragon Wear IPQ4019, MDM9206, MDM9607, MDM9615, MDM9625, MDM9635M, MDM9640, MDM9650, MDM9655, MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 615/16/SD 415, SD 820, and SDX20, buffer overflow vulnerability exist in Sahara boot when program header are parsing.

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

Buffer overflow vulnerability in Qualcomm's Sahara bootloader component during program header parsing. This pre-OS vulnerability affects multiple Snapdragon mobile and wearable chipsets, potentially allowing arbitrary code execution in the boot chain before the Android OS loads.

MitigationApply Android security patch level 2018-04-05 or later from the device OEM, which contains the patched Sahara bootloader firmware. For enterprise environments, identify affected devices and coordinate firmware updates through manufacturers or carriers.

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
Mdm9615 FirmwareOperating system
Affected:all versions
Mdm9625 FirmwareOperating system
Affected:all versions
Mdm9635m FirmwareOperating system
Affected:all versions
Mdm9640 FirmwareOperating system
Affected:all versions
Ipq4019 FirmwareOperating system
Affected:all versions
Mdm9650 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 device chipset model
    Check the device specifications, system information, or bootloader identification to determine the Qualcomm chipset model (e.g., Mdm9206, Mdm9607, Mdm9615, Mdm9625, Mdm9635m, Mdm9640, Ipq4019, or Mdm9650). On Android devices, this may appear in /proc/cpuinfo, boot logs, or OEM documentation.
    Affected if The chipset matches one of the following: Mdm9206, Mdm9607, Mdm9615, Mdm9625, Mdm9635m, Mdm9640, Ipq4019, or Mdm9650.
  2. Determine Android security patch level
    Check the device's Android security patch level in Settings > About Phone > Android security patch level, or retrieve via 'adb shell getprop ro.build.version.security_patch'. Compare this date to 2018-04-05.
    Affected if The Android security patch level is earlier than 2018-04-05, indicating the vulnerable Sahara bootloader firmware has not been patched.
  3. Verify bootloader version if accessible
    If you have low-level access to the device firmware or bootloader, extract and inspect the Sahara bootloader binary. Check the version string or build date within the bootloader image.
    Affected if The Sahara bootloader version predates the 2018-04-05 patch date, or the firmware has not been updated by the OEM.
  4. Review device inventory for enterprise deployment
    For enterprise mobile device management (MDM) systems, query the device fleet for chipset models and firmware/bootloader update status. Cross-reference with the list of affected Qualcomm chipsets.
    Affected if Managed devices contain any of the affected chipsets (Mdm9206, Mdm9607, Mdm9615, Mdm9625, Mdm9635m, Mdm9640, Ipq4019, Mdm9650) without documented bootloader firmware updates applied.

The device is affected if it contains a Qualcomm chipset from the affected list (Mdm9206, Mdm9607, Mdm9615, Mdm9625, Mdm9635m, Mdm9640, Ipq4019, or Mdm9650) and does not have a bootloader firmware update corresponding to the Android security patch level 2018-04-05 or later.

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 Android security patch level 2018-04-05 or later from the device OEM, which contains the patched Sahara bootloader firmware. For enterprise environments, identify affected devices and coordinate firmware updates through manufacturers or carriers.

Recommended fix High confidence

Android devices with April 5, 2018 security patch level or later; or devices running Android 8.0+ with current security updates

  1. 1. Identify the current Android security patch level on the device (Settings > About Phone > Security Patch Level)
  2. 2. If the device has a security patch level earlier than April 5, 2018, check with the device manufacturer for an available update
  3. 3. Apply the latest available Android security update from the device manufacturer that includes the April 2018 security patch level or later
  4. 4. Verify after update that the Security Patch Level shows April 5, 2018 or later
  5. 5. If no update is available from the manufacturer, consider replacing the device with a model that receives current security updates
Caveat Users should ensure backup of important data before performing system updates; some older devices may not receive the update and will need replacement

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

Fix this in Mdm9206 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA6.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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