dbcve.org
Mdm9206 FirmwareOperating system · Qualcomm

CVE-2014-10062

HIGH · 7.5 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 →
84/100
Remediation priority · High
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, MDM9640, 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, LocationService is being exported, which is a way for a service to expose its methods to other services. This makes it possible for any other services to import LocationService and call into the exposed method for bringing up a data connection.

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 LocationService in Android on affected Qualcomm Snapdragon chipsets is exported, exposing its methods to other services. This allows any application or service to import LocationService and invoke the exposed method to bring up a data connection without authorization, resulting in potential unauthorized network access.

MitigationSet the android:exported attribute to 'false' for the LocationService in AndroidManifest.xml, or implement proper permission checks and authorization for any exported methods.

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
Mdm9640 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

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
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 in the device
    Check the device specifications or use commands like 'cat /proc/cpuinfo' or 'getprop ro.hardware' to identify the chipset. For Android devices, check Settings > About Phone > Hardware/Processor or use 'dmesg | grep -i qualcomm'
    Affected if The device uses any of the following chipsets: Mdm9206, Mdm9607, Mdm9640, Mdm9650, Msm8909w, Sd 210, Sd 212, or Sd 205 firmware
  2. Locate the LocationService component in AndroidManifest.xml
    Inspect the AndroidManifest.xml file in the system firmware or the application that exposes LocationService. Search for a service declaration with 'LocationService' as the name or within the location-related package
    Affected if A <service> element named LocationService is found in the manifest with android:exported not explicitly set to false
  3. Verify the exported status of the LocationService
    Check the android:exported attribute on the LocationService component. If android:exported is missing, it defaults to true when intent-filters are present, or can be checked via 'dumpsys package <pkg>' for installed components
    Affected if android:exported is set to true or is absent without android:exported=false being set, allowing other apps to bind to this service
  4. Check for permission enforcement on LocationService methods
    Review the service code or decompile the APK to inspect the onBind or onStartCommand methods. Verify if android:permission or custom permission checks are performed before allowing data connection activation
    Affected if No android:permission attribute is defined and no programmatic permission checks are performed in the service methods that trigger data connections
  5. Confirm the vulnerable method is accessible
    Use 'dumpsys package' or review the AIDL interface definitions to confirm the LocationService exposes methods that can bring up data connections without user interaction
    Affected if The service exposes methods that can initiate network/data connections accessible to any local application

The device is affected if it uses any of the listed Qualcomm chipset firmware versions AND the LocationService component has android:exported set to true or defaults to true, allowing unauthorized apps to trigger data connections.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Set the android:exported attribute to 'false' for the LocationService in AndroidManifest.xml, or implement proper permission checks and authorization for any exported methods.

Fix this in Mdm9206 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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