dbcve.org
Mdm9206 FirmwareOperating system · Qualcomm

CVE-2014-10048

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 MDM9206, MDM9607, MDM9650, MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 425, SD 430, SD 450, SD 600, SD 615/16/SD 415, SD 617, SD 625, SD 650/52, SD 800, SD 808, SD 810, SD 820, SD 835, and SDX20, while setting the offsets, time-services allows the user to set bases greater than valid base value which will lead to array index out-of-bound.

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

In Android time-services on multiple Qualcomm Snapdragon chipsets (including MDM9206, MDM9607, SD 820, SD 835, and others), improper validation allows users to set offset bases greater than the valid base value, causing an array index out-of-bounds condition that could allow arbitrary memory writes or code execution.

MitigationApply Android security patches from April 2018 or later, which contain the corrected bounds checking in the time-services component for affected Qualcomm chipsets.

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
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 chipset model
    Check the device specifications or use 'getprop ro.board.platform' or 'getprop ro.hardware' to identify the Qualcomm Snapdragon chipset in use
    Affected if The chipset matches one of the affected models: MDM9206, MDM9607, MDM9650, Msm8909w, SD 210, SD 212, SD 205, or SD 400
  2. Verify Android security patch level
    Check the system security patch level using 'getprop ro.build.version.security_patch' or by checking Settings > About Phone > Android security patch level
    Affected if The security patch level is earlier than April 2018, meaning the bounds checking fix has not been applied
  3. Confirm time-services component is present
    Check if the time-services APK or service is installed on the device by examining '/system/framework/time.jar' or checking running services with 'dumpsys' for time-related services
    Affected if The time-services component exists and is accessible to user-space applications
  4. Check firmware version details
    Retrieve firmware version using 'getprop ro.build.version.firmware' or 'getprop' commands specific to the Qualcomm chipset version
    Affected if The firmware version corresponds to a build before the April 2018 security update

A device is likely affected if it uses one of the listed Qualcomm chipsets AND has not received the April 2018 or later Android security patch, as the vulnerable time-services component with improper bounds checking is present.

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 patches from April 2018 or later, which contain the corrected bounds checking in the time-services component for affected Qualcomm chipsets.

Recommended fix High confidence

Android security patch level April 2018 or later (2018-04-05)

  1. Identify the specific device model containing the affected Qualcomm component (MDM9206, MDM9607, MDM9650, MSM8909W, SD 210/212/205/400, or other listed variants)
  2. Contact the device manufacturer or original equipment manufacturer (OEM) to obtain a firmware update
  3. Apply the OEM-provided firmware update that includes the April 2018 Android security patch level or later
  4. Verify the device is running Android security patch level dated 2018-04-05 or later after the update
Caveat Firmware updates for embedded modem/processor components may require OEM support; cannot be obtained directly from Google or Qualcomm

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-10048 — 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-10048 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