CVE-2017-15841: Medium severity Google Android vulnerability

Published Jul 2, 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, SnapdragonHighMed2016.

Affected Software

33 affected components
Google Android
Qualcomm Sd 410 Firmware
Qualcomm SD 410
Qualcomm Sd 412 Firmware
Qualcomm Sd 412
Qualcomm Sd 425 Firmware
Qualcomm SD 425
Qualcomm Sd 427 Firmware
Qualcomm SD 427
Qualcomm Sd 430 Firmware
Qualcomm SD 430
Qualcomm Sd 435 Firmware
Qualcomm SD 435
Qualcomm Sd 450 Firmware
Qualcomm SD 450
Qualcomm Sd 615 Firmware
Qualcomm SD 615
Qualcomm Sd 616 Firmware
Qualcomm Sd 616
Qualcomm Sd 415 Firmware
Qualcomm SD 415
Qualcomm Sd 625 Firmware
Qualcomm SD 625
Qualcomm Sd 650 Firmware
Qualcomm SD 650
Qualcomm Sd 652 Firmware
Qualcomm Sd 652
Qualcomm Sd 820 Firmware
Qualcomm SD 820
Qualcomm Sd 835 Firmware
Qualcomm SD 835
Qualcomm Snapdragon High Med 2016 Firmware
Qualcomm Snapdragon High Med 2016

Event History

Jul 2, 2018
CVE Published
via Android·12:00 AM
Data Sourced
via Android·12:00 AM
SeverityAffected Software
May 6, 2019
CVE Published
via MITRE·10:23 PM
Data Sourced
via MITRE·10:23 PM
DescriptionWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

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.

2

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.

3

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.

4

Is there a workaround for CVE-2017-15841?

There are no known workarounds for CVE-2017-15841; patching the firmware is the recommended solution.

5

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203