CVE-2019-14028: High severity Google Android vulnerability
Buffer overwrite during memcpy due to lack of check on SSID length validation in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking in APQ8009, APQ8017, APQ8053, APQ8064, APQ8096, APQ8096AU, APQ8098, IPQ6018, IPQ8074, MDM9206, MDM9207C, MDM9607, MDM9640, MDM9650, MSM8996AU, MSM8998, Nicobar, QCA4531, QCA6174A, QCA6564, QCA6574, QCA6574AU, QCA6584, QCA6584AU, QCA8081, QCA9377, QCA9379, QCA9886, QCN7605, QCS404, QCS405, QCS605, Rennell, SA6155P, SC8180X, SDA660, SDA845, SDM630, SDM636, SDM660, SDM670, SDM710, SDM845, SDM850, SDX20, SDX24, SM6150, SM7150, SM8150, SM8250, SXR1130, SXR2130
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2019-14028?
CVE-2019-14028 has been assigned a high severity rating due to its potential impact on device security.
How do I fix CVE-2019-14028?
To fix CVE-2019-14028, apply the latest firmware updates provided by Qualcomm for your affected device.
Which devices are affected by CVE-2019-14028?
CVE-2019-14028 affects various Qualcomm chipsets including Snapdragon series used in mobile and IoT devices.
Is CVE-2019-14028 exploitable remotely?
Yes, CVE-2019-14028 can potentially be exploited remotely, making it crucial to address this vulnerability.
What symptoms indicate that CVE-2019-14028 has been exploited?
Symptoms of a successful exploitation of CVE-2019-14028 may include unexpected behavior or crashes in affected devices.