dbcve.org
Sd 410 FirmwareOperating system · Qualcomm

CVE-2015-9173

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 SD 410/12, SD 617, SD 650/52, SD 800, SD 808, and SD 810, missing of return value check in memscpy can cause memory corruption in TQS App.

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

A missing return value check on the memscpy function in the TQS App running on affected Qualcomm Snapdragon processors (SD 410/12, SD 617, SD 650/52, SD 800, SD 808, SD 810) allows memory corruption. The memscpy function returns the destination pointer, and not checking this return value can lead to buffer overflows or improper memory handling.

MitigationApply Android security patch level 2018-04-05 or later to affected devices. For end-of-life devices that cannot receive updates, consider replacing with devices receiving regular security updates.

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
Sd 410 FirmwareOperating system
Affected:all versions
Sd 412 FirmwareOperating system
Affected:all versions
Sd 617 FirmwareOperating system
Affected:all versions
Sd 650 FirmwareOperating system
Affected:all versions
Sd 652 FirmwareOperating system
Affected:all versions
Sd 800 FirmwareOperating system
Affected:all versions
Sd 808 FirmwareOperating system
Affected:all versions
Sd 810 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 processor model
    Check the device specifications or use system information tools (e.g., /proc/cpuinfo on Android, or manufacturer documentation) to determine the exact Snapdragon model number
    Affected if The processor is any of: SD 410, SD 412, SD 617, SD 650, SD 652, SD 800, SD 808, or SD 810
  2. Check the firmware version
    Retrieve the firmware version from the device settings (About Phone > Build Number) or via ADB with command: getprop ro.build.version.full or getprop ro.build.version.security_patch
    Affected if The firmware is any version (all versions of these models are affected per the CVE)
  3. Verify TQS App presence
    Check if the TQS App is installed on the device. On Android, list installed packages using: pm list packages | grep tqs or check /data/data or /system/app directories for TQS-related APKs
    Affected if The TQS App is present on the device (the vulnerable memscpy function resides in this application)

A user is affected if their device contains a Qualcomm Snapdragon processor from the SD 410/412/617/650/652/800/808/810 family and has the TQS App installed with the vulnerable memscpy implementation.

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 to affected devices. For end-of-life devices that cannot receive updates, consider replacing with devices receiving regular security updates.

Recommended fix High confidence

Android Security Patch Level April 2018 or later (2018-04-05)

  1. Check the device's current Android Security Patch Level in Settings > About Phone > Software Information > Security Patch Level
  2. If the Security Patch Level is earlier than April 5, 2018, apply any available system updates from the device manufacturer
  3. Verify that the device has Android Security Patch Level dated 2018-04-05 or later after updating
  4. If no update is available from the device manufacturer, consider upgrading to a device model that receives regular security updates
Caveat Some older devices may no longer receive security updates from manufacturers and may need to be replaced

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

Fix this in Sd 410 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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