CVE-2019-10609: Critical severity Google Android vulnerability
Out of bound write can happen due to lack of check of array index value while calculating it. in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables in APQ8009, APQ8017, APQ8053, APQ8076, APQ8096, APQ8096AU, APQ8098, MDM9150, MDM9205, MDM9206, MDM9607, MDM9615, MDM9635M, MDM9640, MDM9645, MDM9650, MDM9655, MSM8905, MSM8909, MSM8909W, MSM8917, MSM8920, MSM8937, MSM8940, MSM8953, MSM8996AU, MSM8998, Nicobar, QCM2150, QCS605, QM215, Rennell, SC7180, SC8180X, SDA660, SDA845, SDM429, SDM429W, SDM439, SDM450, SDM630, SDM632, SDM636, SDM660, SDM670, SDM710, SDM845, SDM850, SDX20, SDX24, SDX55, SM6150, SM7150, SM8150, SXR1130
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2019-10609?
CVE-2019-10609 has a high severity rating due to its potential to allow out-of-bounds write vulnerabilities.
How do I fix CVE-2019-10609?
To fix CVE-2019-10609, update the affected Qualcomm firmware to the latest version provided by the vendor.
What products are affected by CVE-2019-10609?
CVE-2019-10609 affects various Qualcomm products including Snapdragon Auto, Snapdragon Mobile, and Snapdragon Industrial IOT, among others.
Is CVE-2019-10609 publicly disclosed?
Yes, CVE-2019-10609 has been publicly disclosed and documented in security bulletins by Qualcomm and Android.
What are the implications of CVE-2019-10609?
The implications of CVE-2019-10609 include potential exploitation that could lead to unauthorized access and system compromise if not patched.