CVE-2019-2275: Buffer Overflow
While deserializing any key blob during key operations, buffer overflow could occur exposing partial key information if any key operations are invoked(Depends on CVE-2018-13907) 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 Wearables, Snapdragon Wired Infrastructure and Networking in MDM9150, MDM9205, MDM9206, MDM9607, MDM9650, MSM8909W, MSM8996AU, QCS404, QCS605, Qualcomm 215, SD 210/SD 212/SD 205, SD 410/12, SD 425, SD 427, SD 430, SD 435, SD 439 / SD 429, SD 450, SD 625, SD 632, SD 636, SD 650/52, SD 712 / SD 710 / SD 670, SD 820, SD 820A, SD 835, SD 845 / SD 850, SD 855, SD 8CX, SDA660, SDM439, SDM630, SDM660, SnapdragonHighMed2016, SXR1130
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2019-2275?
The severity of CVE-2019-2275 is classified as high due to the potential for buffer overflow leading to exposure of partial key information.
How do I fix CVE-2019-2275?
To fix CVE-2019-2275, ensure that you update to the latest firmware or software version provided by the vendor that addresses this vulnerability.
What systems are affected by CVE-2019-2275?
CVE-2019-2275 affects several Qualcomm Snapdragon platforms, including Snapdragon Auto, Snapdragon Compute, and various firmware versions.
What does CVE-2019-2275 exploit?
CVE-2019-2275 exploits a buffer overflow vulnerability that can occur during key blob deserialization in key operations.
Is there a workaround for CVE-2019-2275?
Currently, there are no known workarounds for CVE-2019-2275, so applying the patch or update from the vendor is essential.