dbcve.org
Mdm9615 FirmwareOperating system · Qualcomm

CVE-2014-10059

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 MDM9615, MDM9625, SD 210/SD 212/SD 205, SD 400, and SD 800, improper access control on ATCMD service allows third party services to access without user knowledge.

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

Improper access control in the ATCMD (AT Command) service on affected Qualcomm Snapdragon processors (MDM9615, MDM9625, SD 210/SD 212/SD 205, SD 400, SD 800) allows third-party applications to access the AT command interface without user knowledge, potentially enabling unauthorized access to modem functions.

MitigationApply Android security patch level from 2018-04-05 or later; for out-of-support devices, consider network segmentation or device replacement to mitigate exposure.

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
Mdm9615 FirmwareOperating system
Affected:all versions
Mdm9625 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
Sd 800 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 device processor model
    Check the processor/chipset by running 'cat /proc/cpuinfo' on the device or look in Settings > About Phone > Processor or Hardware info
    Affected if The processor is one of: MDM9615, MDM9625, SD 210, SD 212, SD 205, SD 400, or SD 800
  2. Verify ATCMD service availability
    Check if the AT command service is accessible by examining running services (via 'dumpsys' or 'ps' commands) or by testing if /dev/smd0 or similar AT command device nodes exist and are world-accessible
    Affected if The ATCMD service interface (/dev/smd* device nodes) is exposed and accessible to third-party applications without privilege checks
  3. Check Android security patch level
    Go to Settings > About Phone > Android security patch level, or run 'getprop ro.build.version.security_patch'
    Affected if The security patch level is earlier than 2018-04-05 (patch levels after this date contain the fix)
  4. Review app permissions for AT command access
    Audit installed applications for those holding ATCMD or radio permissions (e.g., android.permission.MODIFY_PHONE_STATE or carrier-specific permissions)
    Affected if Applications without proper privilege have been granted access to the AT command interface

The device is affected if it uses any of the listed Qualcomm Snapdragon processors (MDM9615, MDM9625, SD 210/212/205/400/800) AND the ATCMD service is exposed, especially when the Android security patch level predates the 2018-04-05 update.

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 from 2018-04-05 or later; for out-of-support devices, consider network segmentation or device replacement to mitigate exposure.

Recommended fix High confidence

Android security patch level 2018-04-05 or later from device OEM

  1. Check the current Android security patch level on the device in Settings > About Phone > Security patch level
  2. Contact the device manufacturer (OEM) to obtain an Android security update that includes the April 2018 security patch level or later
  3. Apply the manufacturer-provided security update through the device's standard software update mechanism
  4. Verify after update that the security patch level shows April 2018 (2018-04-05) or later
Caveat Older devices may no longer receive security updates from OEMs; some devices may be end-of-life and require replacement

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

Fix this in Mdm9615 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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