dbcve.org
Sd 410 FirmwareOperating system · Qualcomm

CVE-2017-15841

MEDIUM · 5.5 CVSS v3.0 Published 2019-05-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
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
When HOST sends a Special command ID packet, Controller triggers a RAM Dump and FW reset in Snapdragon Mobile in version SD 410/12, SD 425, SD 427, SD 430, SD 435, SD 450, SD 615/16/SD 415, SD 625, SD 650/52, SD 820, SD 835, Snapdragon_High_Med_2016.

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 denial of service vulnerability exists in the Controller component of Qualcomm Snapdragon mobile chipsets. When the HOST system sends a specially crafted 'Special command ID packet', it triggers an unintended RAM dump and firmware reset. This affects multiple Snapdragon variants including SD 410/12, SD 425, SD 427, SD 430, SD 435, SD 450, SD 615/16/SD 415, SD 625, SD 650/52, SD 820, SD 835, and Snapdragon_High_Med_2016.

MitigationApply firmware/security updates provided by OEM/device manufacturers. This is a firmware-level vulnerability requiring patches from Qualcomm and subsequent distribution through device vendors. Users should ensure their devices receive the latest security patches.

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 425 FirmwareOperating system
Affected:all versions
Sd 427 FirmwareOperating system
Affected:all versions
Sd 430 FirmwareOperating system
Affected:all versions
Sd 435 FirmwareOperating system
Affected:all versions
Sd 450 FirmwareOperating system
Affected:all versions
Sd 615 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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 Snapdragon chipset model
    Check your device settings or use a system information app to determine the exact Snapdragon chipset model. On Android, this is typically found in Settings > About Phone > Hardware/Processor, or using apps like CPU-Z or AIDA64.
    Affected if The chipset is one of: SD 410, SD 412, SD 425, SD 427, SD 430, SD 435, SD 450, SD 615, SD 616, SD 415, SD 625, SD 650, SD 652, SD 820, SD 835, or Snapdragon_High_Med_2016 variants.
  2. Determine the firmware version
    Access the modem/baseband firmware version through Settings > About Phone > Baseband version, or use diagnostic codes like *#*#4636#*#* on Android devices. The exact path varies by device manufacturer.
    Affected if Any firmware version is listed since the advisory states all versions of the listed firmware builds are affected.
  3. Check if the Controller component is accessible
    This vulnerability requires a specially crafted packet from the HOST system to trigger. For mobile devices, this typically means the cellular modem/baseband controller. Verify the baseband/modem firmware is active by checking for cellular connectivity.
    Affected if The device has an active cellular/modem subsystem using the affected Snapdragon Controller component.
  4. Verify vendor security patch level
    Check your device's Android Security Patch Level in Settings > About Phone > Security Patch Level. This indicates whether the OEM has applied the Qualcomm firmware updates.
    Affected if The security patch level is earlier than the vendor release that includes the CVE-2017-15841 fix (specific dates vary by OEM).

If your device uses an affected Snapdragon chipset model with cellular capability and has not received vendor firmware/security updates addressing this CVE, you are potentially affected by the RAM dump and firmware reset denial of service condition.

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

Apply firmware/security updates provided by OEM/device manufacturers. This is a firmware-level vulnerability requiring patches from Qualcomm and subsequent distribution through device vendors. Users should ensure their devices receive the latest security patches.

Fix this in Sd 410 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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