CVE-2019-14033: Critical severity Google Android vulnerability
Multiple Read overflows issue due to improper length check while decoding tau reject/tau accept/detach request/attach reject/attach accept in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables in APQ8053, APQ8096, APQ8096AU, APQ8098, MDM9150, MDM9205, MDM9206, MDM9607, MDM9615, MDM9625, 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-14033?
CVE-2019-14033 has a high severity rating due to potential read overflow vulnerabilities that could lead to data corruption or unintended behavior.
How do I fix CVE-2019-14033?
To mitigate CVE-2019-14033, update the affected Qualcomm firmware and ensure that you are running the latest version of Android.
What systems are affected by CVE-2019-14033?
CVE-2019-14033 affects various Qualcomm chipsets, including those used in Snapdragon Auto, Snapdragon Compute, and Qualcomm mobile devices.
Can CVE-2019-14033 be exploited remotely?
Yes, CVE-2019-14033 could potentially be exploited remotely, allowing attackers to execute arbitrary code on affected devices.
What are the best practices to prevent CVE-2019-14033 vulnerabilities?
Maintain up-to-date software and firmware on devices to minimize the risk of vulnerabilities like CVE-2019-14033.