First published: Wed Dec 18 2019(Updated: )
Out of boundary access is possible as there is no validation of data accessed against the received size of the packet in case of malicious firmware in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables in APQ8009, APQ8017, APQ8053, APQ8096AU, APQ8098, MDM9206, MDM9207C, MDM9607, MDM9640, MDM9650, MSM8909W, MSM8917, MSM8920, MSM8937, MSM8940, MSM8953, MSM8996AU, MSM8998, Nicobar, QCN7605, QCS405, QCS605, QM215, SA6155P, SDA660, SDA845, SDM429, SDM439, SDM450, SDM630, SDM632, SDM636, SDM660, SDM670, SDM710, SDM845, SDX20, SDX24, SDX55, SM6150, SM7150, SM8150, SM8250, SXR1130, SXR2130
Credit: product-security@qualcomm.com
Affected Software | Affected Version | How to fix |
---|---|---|
Qualcomm APQ8009W Firmware | ||
Qualcomm APQ8009W | ||
Qualcomm APQ8017 | ||
Qualcomm APQ8017 | ||
qualcomm apq8053-ac firmware | ||
Qualcomm APQ8053 Firmware | ||
Qualcomm APQ8096AU Firmware | ||
Qualcomm APQ8096AU Firmware | ||
qualcomm APQ8098 | ||
Qualcomm 8098 | ||
Qualcomm MDM9206 | ||
Qualcomm MDM9206 firmware | ||
qualcomm MDM9207C firmware | ||
Qualcomm 9207 LTE Modem | ||
Qualcomm MD9607 Firmware | ||
Qualcomm MDM9607 firmware | ||
qualcomm mdm9640 firmware | ||
Qualcomm MDM9640 | ||
Qualcomm MDM9650 | ||
Qualcomm MDM9650 firmware | ||
Qualcomm MSM8909W | ||
Qualcomm Snapdragon 8909 | ||
Qualcomm MSM8917 | ||
Qualcomm MSM8917 Firmware | ||
Qualcomm 8920 Firmware | ||
Qualcomm 8920 | ||
Qualcomm 8937 Firmware | ||
qualcomm MSM8937 firmware | ||
qualcomm MSM8940 firmware | ||
Qualcomm 8940 | ||
Qualcomm 8953 Firmware | ||
Qualcomm MSM8953 Firmware | ||
qualcomm MSM8996AU firmware | ||
Qualcomm MSM8996AU Firmware | ||
Qualcomm MSM8998 | ||
Qualcomm 8998 | ||
Qualcomm Nicobar | ||
Qualcomm Nicobar | ||
Qualcomm QCN7605 Firmware | ||
Qualcomm QCN7605 Firmware | ||
Qualcomm QCS405 Firmware | ||
Qualcomm QCS405 Firmware | ||
Qualcomm ZZ QCS605 firmware | ||
Qualcomm QCS605 Firmware | ||
Qualcomm 215 Firmware | ||
Qualcomm 215 | ||
Qualcomm SA6155 | ||
Qualcomm SA6155P | ||
Qualcomm SDA660 | ||
Qualcomm SDA660 | ||
Qualcomm SD845 Firmware | ||
Qualcomm Snapdragon 845 | ||
Qualcomm SDM429W | ||
Qualcomm SD429 | ||
qualcomm SDM439 firmware | ||
Qualcomm SDM439 Firmware | ||
Qualcomm SD 450 Firmware | ||
Qualcomm Snapdragon 450 | ||
qualcomm SDM630 firmware | ||
qualcomm SDM630 | ||
Qualcomm SDM632 | ||
Qualcomm SDM632 | ||
Qualcomm SD 636 Firmware | ||
Qualcomm SDM636 Firmware | ||
Qualcomm SD660 Firmware | ||
Qualcomm Snapdragon 660 | ||
Qualcomm SD 670 Firmware | ||
Qualcomm SDM670 Firmware | ||
Qualcomm SD710 Firmware | ||
Qualcomm Snapdragon 710 | ||
Qualcomm SDA/SDM845 Firmware | ||
Qualcomm Snapdragon 845 | ||
Qualcomm SDX20 Firmware | ||
Qualcomm SDX20 Firmware | ||
Qualcomm SDX24 | ||
Qualcomm SDX24 | ||
Qualcomm SDX55M Firmware | ||
Qualcomm SDX55 Firmware | ||
qualcomm SM6150P firmware | ||
Qualcomm SM6150P | ||
qualcomm SM7150 firmware | ||
qualcomm SM7150 firmware | ||
Qualcomm SM8150P Firmware | ||
Qualcomm SM8150 Fusion | ||
Qualcomm SM8250 | ||
Qualcomm qsm8250 | ||
Qualcomm SXR1130 | ||
Qualcomm SXR1130 Firmware | ||
qualcomm SXR2130P firmware | ||
Qualcomm SXR2130 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2019-10614 is considered to have a high severity due to the potential for out-of-bounds access and the risk it poses to affected Qualcomm devices.
To fix CVE-2019-10614, you should update the firmware of affected Qualcomm devices to the latest version provided by Qualcomm that addresses this vulnerability.
CVE-2019-10614 affects a range of Qualcomm devices including various Snapdragon platforms such as the apq8009, apq8017, and many others listed in the bulletin.
The risk associated with CVE-2019-10614 includes unauthorized access to sensitive data and potential control over affected devices due to improper validation of incoming packets.
As of the last reported assessment, there are no confirmed cases of CVE-2019-10614 being actively exploited in the wild, but the vulnerability remains a serious concern.