dbcve.org
Mdm9615 FirmwareOperating system · Qualcomm

CVE-2014-10046

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, MDM9635M, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 615/16/SD 415, SD 800, SD 808, and SD 810, use after free vulnerability when the PDN throttle info block is freed without clearing the corresponding active timer.

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

Use-after-free vulnerability in Qualcomm Snapdragon baseband processors where the PDN throttle info block is freed without clearing the corresponding active timer, allowing memory access after deallocation and potentially enabling arbitrary code execution.

MitigationApply vendor security patches released on or after 2018-04-05; for embedded systems using affected Snapdragon variants, obtain and deploy firmware updates from Qualcomm.

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
Mdm9635m 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 410 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 Qualcomm baseband processor model
    Check system hardware information through AT commands (AT+CGMM, AT+CGMI) or diagnostic logs to identify the baseband/modem chipset. For mobile devices, check /proc/cpuinfo or device specs. For embedded systems, review hardware BOM or module documentation.
    Affected if The identified chipset matches Mdm9615, Mdm9625, Mdm9635m, Sd 210, Sd 212, Sd 205, Sd 400, or Sd 410
  2. Verify baseband firmware version
    Query the baseband processor firmware version using manufacturer-specific AT commands (such as AT+CGMR or through Qualcomm QDSA diagnostic interface) or check modem firmware information in system logs.
    Affected if The baseband firmware is present on any of the affected chipset models listed (all versions are affected)

The environment is affected if any device or system utilizes one of the listed Qualcomm Snapdragon baseband processors (Mdm9615, Mdm9625, Mdm9635m, Sd 210, Sd 212, Sd 205, Sd 400, or Sd 410).

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 security patches released on or after 2018-04-05; for embedded systems using affected Snapdragon variants, obtain and deploy firmware updates from Qualcomm.

Recommended fix High confidence

Any Android device with security patch level April 5, 2018 or later

  1. Check the device's current Android security patch level in Settings > About Phone > Security Patch Level
  2. If the security patch level is earlier than April 5, 2018, check for system updates via Settings > System > Software Update or Settings > About Phone > Software Update
  3. Apply any available Android system updates that include the April 2018 security patch level or later
  4. If no carrier or manufacturer update is available, consider upgrading to a device that receives current security patches
  5. For embedded/MDM products using these chipsets, contact the device manufacturer for a firmware update that includes the April 2018 Qualcomm security fix
Caveat Older devices may not receive further updates; some may need hardware replacement if no firmware patch is available from the manufacturer

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
  • Testing8.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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