CVE-2017-15841
First published: Mon Jul 02 2018(Updated: )
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.
Credit: product-security@qualcomm.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Android | ||
| Qualcomm SD410 Firmware | ||
| Qualcomm Snapdragon 410 | ||
| Qualcomm SD412 Firmware | ||
| Qualcomm SD412 | ||
| Qualcomm SDR425 Firmware | ||
| Qualcomm Snapdragon 425 | ||
| Qualcomm SD427 Firmware | ||
| Qualcomm SD 427 firmware | ||
| Qualcomm SD 430 Firmware | ||
| Qualcomm SD 430 Firmware | ||
| qualcomm sd435 firmware | ||
| Qualcomm Snapdragon 435 | ||
| Qualcomm SDM450 Firmware | ||
| Qualcomm SDM450 | ||
| Qualcomm SD615 Firmware | ||
| Qualcomm Snapdragon 615 | ||
| Qualcomm SD 616 Firmware | ||
| Qualcomm Snapdragon 616 | ||
| Qualcomm Snapdragon 415 Firmware | ||
| Qualcomm Snapdragon 415 | ||
| Qualcomm SD 625 Firmware | ||
| Qualcomm Snapdragon 625 | ||
| Qualcomm SD650 Firmware | ||
| Qualcomm Snapdragon 650 | ||
| Qualcomm SD652 Firmware | ||
| Qualcomm SD652 Firmware | ||
| Qualcomm SD820 Firmware | ||
| Qualcomm SD820 Firmware | ||
| Qualcomm SD835 Firmware | ||
| Qualcomm Snapdragon 835 | ||
| Qualcomm Snapdragon High Med 2016 | ||
| Qualcomm Snapdragon High Med 2016 Firmware |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2017-15841?
CVE-2017-15841 is classified as a high-severity vulnerability due to its potential to facilitate a RAM dump and firmware reset.
How do I fix CVE-2017-15841?
To mitigate CVE-2017-15841, update the affected Qualcomm firmware to the latest secure version provided by Qualcomm.
Which devices are affected by CVE-2017-15841?
CVE-2017-15841 impacts numerous Qualcomm Snapdragon chipsets including SD 410, SD 425, SD 430, and others.
Is there a workaround for CVE-2017-15841?
There are no known workarounds for CVE-2017-15841; patching the firmware is the recommended solution.
What could happen if CVE-2017-15841 is exploited?
Exploiting CVE-2017-15841 could allow an attacker to perform unauthorized operations such as a RAM dump and firmware reset.
- agent/type
- agent/first-publish-date
- agent/references
- agent/severity
- agent/author
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/event
- agent/last-modified-date
- agent/source
- agent/tags
- collector/android-source
- source/Android
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- agent/softwarecombine
- collector/nvd-index
- vendor/google
- canonical/android
- vendor/qualcomm
- canonical/qualcomm sd410 firmware
- canonical/qualcomm snapdragon 410
- canonical/qualcomm sd412 firmware
- canonical/qualcomm sd412
- canonical/qualcomm sdr425 firmware
- canonical/qualcomm snapdragon 425
- canonical/qualcomm sd427 firmware
- canonical/qualcomm sd 427 firmware
- canonical/qualcomm sd 430 firmware
- canonical/qualcomm sd435 firmware
- canonical/qualcomm snapdragon 435
- canonical/qualcomm sdm450 firmware
- canonical/qualcomm sdm450
- canonical/qualcomm sd615 firmware
- canonical/qualcomm snapdragon 615
- canonical/qualcomm sd 616 firmware
- canonical/qualcomm snapdragon 616
- canonical/qualcomm snapdragon 415 firmware
- canonical/qualcomm snapdragon 415
- canonical/qualcomm sd 625 firmware
- canonical/qualcomm snapdragon 625
- canonical/qualcomm sd650 firmware
- canonical/qualcomm snapdragon 650
- canonical/qualcomm sd652 firmware
- canonical/qualcomm sd820 firmware
- canonical/qualcomm sd835 firmware
- canonical/qualcomm snapdragon 835
- canonical/qualcomm snapdragon high med 2016
- canonical/qualcomm snapdragon high med 2016 firmware