First published: Mon Dec 02 2019(Updated: )
Device memory may get corrupted because of buffer overflow/underflow. in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables in APQ8009, APQ8016, APQ8017, APQ8053, APQ8096, APQ8096AU, APQ8098, MDM9150, MDM9607, MDM9615, MDM9625, MDM9635M, MDM9640, MDM9645, MDM9650, MDM9655, MSM8905, MSM8909, MSM8909W, MSM8917, MSM8920, MSM8937, MSM8939, MSM8940, MSM8953, MSM8996AU, MSM8998, Nicobar, QCM2150, QCS605, QM215, SDA660, SDA845, SDM429, SDM439, SDM450, SDM630, SDM632, SDM636, SDM660, SDM670, SDM710, SDM845, SDM850, SDX20, SM6150, SM7150, SXR1130
Credit: product-security@qualcomm.com
Affected Software | Affected Version | How to fix |
---|---|---|
Qualcomm apq8009 firmware | ||
Qualcomm apq8009 | ||
qualcomm apq8016 firmware | ||
qualcomm apq8016 | ||
Qualcomm apq8017 firmware | ||
Qualcomm apq8017 | ||
Qualcomm APQ8053 Firmware | ||
Qualcomm APQ8053 Firmware | ||
qualcomm APQ8096 firmware | ||
qualcomm APQ8096SG | ||
Qualcomm apq8096au firmware | ||
Qualcomm apq8096au | ||
qualcomm APQ8098 firmware | ||
qualcomm APQ8098 | ||
Qualcomm MDM9150 firmware | ||
Qualcomm MDM9150 | ||
Qualcomm MDM9607 firmware | ||
Qualcomm MDM9607 | ||
Qualcomm MDM9615 firmware | ||
Qualcomm MDM9615 | ||
Qualcomm MDM9625 firmware | ||
Qualcomm MDM9625 | ||
Qualcomm MDM9635M firmware | ||
Qualcomm MDM9635M | ||
qualcomm mdm9640 firmware | ||
qualcomm MDM9640 | ||
qualcomm mdm9645 firmware | ||
qualcomm mdm9645 | ||
Qualcomm MDM9650 firmware | ||
Qualcomm MDM9650 | ||
Qualcomm MDM9655 firmware | ||
Qualcomm MDM9655 | ||
qualcomm MSM8905 firmware | ||
qualcomm MSM8905 | ||
Qualcomm MSM8909W | ||
Qualcomm MSM8909W | ||
Qualcomm MSM8909W | ||
Qualcomm MSM8909W | ||
Qualcomm msm8917 firmware | ||
Qualcomm msm8917 | ||
qualcomm MSM8920 firmware | ||
qualcomm MSM8920 | ||
qualcomm MSM8937 firmware | ||
qualcomm MSM8937 | ||
qualcomm MSM8939 firmware | ||
qualcomm MSM8939 | ||
qualcomm MSM8940 firmware | ||
qualcomm MSM8940 | ||
Qualcomm msm8953 firmware | ||
Qualcomm msm8953 | ||
Qualcomm MSM8996AU Firmware | ||
Qualcomm MSM8996AU Firmware | ||
qualcomm MSM8998 firmware | ||
Qualcomm MSM8998 | ||
qualcomm Nicobar firmware | ||
qualcomm Nicobar | ||
qualcomm QCM2150 firmware | ||
qualcomm QCM2150 | ||
Qualcomm QCS605 firmware | ||
Qualcomm QCS605 | ||
Qualcomm qm215 firmware | ||
Qualcomm qm215 | ||
qualcomm SDA660 firmware | ||
qualcomm SDA660 | ||
qualcomm sda845 firmware | ||
qualcomm sda845 | ||
qualcomm SDM429 firmware | ||
qualcomm SDM429 | ||
qualcomm SDM439 firmware | ||
qualcomm SDM439 | ||
qualcomm SDM450 firmware | ||
Qualcomm SDM450 | ||
qualcomm SDM630 firmware | ||
qualcomm SDM630 | ||
qualcomm SDM632 firmware | ||
qualcomm SDM632 | ||
qualcomm SDM636 firmware | ||
qualcomm SDM636 | ||
qualcomm SDM660 firmware | ||
qualcomm SDM660 | ||
qualcomm sdm670 firmware | ||
qualcomm sdm670 | ||
qualcomm sdm710 firmware | ||
qualcomm sdm710 | ||
qualcomm SDM845 firmware | ||
qualcomm SDM845 | ||
qualcomm sdm850 firmware | ||
qualcomm sdm850 | ||
Qualcomm SDX20 Firmware | ||
Qualcomm SDX20 Firmware | ||
Qualcomm SM6150 | ||
Qualcomm SM6150 Firmware | ||
Qualcomm SM7150 Firmware | ||
qualcomm SM7150 firmware | ||
Qualcomm SXR1130 Firmware | ||
Qualcomm SXR1130 | ||
Android |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2019-2242 has been classified as high severity due to the potential for device memory corruption affecting various Qualcomm products.
To address CVE-2019-2242, users should update their affected Qualcomm devices to the latest firmware version provided by the manufacturer.
CVE-2019-2242 primarily affects devices using Qualcomm Snapdragon SoCs, including multiple variants like APQ8009, APQ8096, and others.
CVE-2019-2242 is categorized as a buffer overflow/underflow vulnerability that may lead to memory corruption.
CVE-2019-2242 does not specify remote exploitability; however, it poses risks if exploited locally due to its nature of affecting device memory.