Qualcomm MDM9207C Firmware vulnerabilities
118 CVEs affecting Qualcomm MDM9207C Firmware, 0 known to be exploited (CISA KEV), with EPSS scores. Latest: CVE-2020-3703, published 2020-11-02.
More from Qualcomm.
Highest priority
Known exploited (CISA KEV) first, then by EPSS exploit probability.
- CVE-2020-3657, published 2020-11-02. Critical severity, CVSS 9.8. EPSS: 28.3% chance of exploitation in the next 30 days. u'Remote code execution can happen by sending a carefully crafted POST query when Device configuration is accessed from a tethered client through webserver due to lack of array bound check.' in…
- CVE-2019-10574, published 2020-04-16. High severity, CVSS 7.1. EPSS: 1.6% chance of exploitation in the next 30 days. Lack of boundary checks for data offsets received from HLOS can lead to out-of-bound read in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics…
- CVE-2019-10557, published 2019-12-18. Critical severity, CVSS 9.8. EPSS: 1.1% chance of exploitation in the next 30 days. Out-of-bound read in the wireless driver in the Linux kernel due to lack of check of buffer length. in Snapdragon Auto, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT,…
- CVE-2019-10581, published 2020-01-21. Critical severity, CVSS 9.8. EPSS: 1.1% chance of exploitation in the next 30 days. NULL is assigned to local instance of audio device pointer after free instead of global static pointer and can lead to use after free issue in Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon…
- CVE-2020-3633, published 2020-06-02. Critical severity, CVSS 9.8. EPSS: 1.1% chance of exploitation in the next 30 days. Array out of bound may occur while playing mp3 file as no check is there on offset if it is greater than the buffer allocated or not in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT,…
- CVE-2019-10532, published 2020-01-21. Critical severity, CVSS 9.8. EPSS: 1.1% chance of exploitation in the next 30 days. Null-pointer dereference issue can occur while calculating string length when source string length is zero in Snapdragon Auto, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial…
- CVE-2020-3641, published 2020-06-02. Critical severity, CVSS 9.8. EPSS: 1.1% chance of exploitation in the next 30 days. Integer overflow may occur if atom size is less than atom offset as there is improper validation of atom size in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial…
- CVE-2019-14006, published 2020-01-21. Critical severity, CVSS 9.8. EPSS: 1% chance of exploitation in the next 30 days. Buffer overflow occur while playing the clip which is nonstandard due to lack of offset length check in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT,…
- CVE-2019-14005, published 2020-01-21. Critical severity, CVSS 9.8. EPSS: 1% chance of exploitation in the next 30 days. Buffer overflow occur while playing the clip which is nonstandard due to lack of check of size duration in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT,…
- CVE-2020-3660, published 2020-06-22. Critical severity, CVSS 9.8. EPSS: 0.9% chance of exploitation in the next 30 days. Possible null-pointer dereference can occur while parsing mp4 clip with corrupted sample table atoms in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT,…
Latest
- CVE-2020-3703, published 2020-11-02. Critical severity, CVSS 9.8. EPSS: 0.7% chance of exploitation in the next 30 days. u'Buffer over-read issue in Bluetooth peripheral firmware due to lack of check for invalid opcode and length of opcode received from central device(This CVE is equivalent to Link Layer Length Overfow…
- CVE-2020-3696, published 2020-11-02. High severity, CVSS 7.8. EPSS: 0.2% chance of exploitation in the next 30 days. u'Use after free while installing new security rule in ipcrtr as old one is deleted and this rule could still be in use for checking security permission for particular process' in Snapdragon Auto,…
- CVE-2020-3666, published 2020-09-08. High severity, CVSS 7.8. EPSS: 0.2% chance of exploitation in the next 30 days. u'Out of bounds memory access during memory copy while processing Host command' in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity,…
- CVE-2020-3624, published 2020-09-08. High severity, CVSS 7.8. EPSS: 0.2% chance of exploitation in the next 30 days. u'A potential buffer overflow exists due to integer overflow when parsing handler options due to wrong data type usage in operation' in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity,…
- CVE-2020-11118, published 2020-09-08. High severity, CVSS 7.5. EPSS: 0.7% chance of exploitation in the next 30 days. u'Information exposure issues while processing IE header due to improper check of beacon IE frame' in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer Electronics Connectivity, Snapdragon…
- CVE-2020-11116, published 2020-09-08. Critical severity, CVSS 9.8. EPSS: 0.9% chance of exploitation in the next 30 days. u'Possible out of bound write while processing association response received from host due to lack of check of IE length' in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer Electronics…
- CVE-2020-11115, published 2020-09-08. High severity, CVSS 7.5. EPSS: 0.7% chance of exploitation in the next 30 days. u'Buffer over read occurs while processing information element from beacon due to lack of check of data received from beacon' in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer Electronics…
- CVE-2019-14074, published 2020-09-08. High severity, CVSS 7.8. EPSS: 0.2% chance of exploitation in the next 30 days. u'Heap overflow in diag command handler due to lack of check of packet length received from user' in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics…
- CVE-2019-10527, published 2020-09-08. High severity, CVSS 7.8. EPSS: 0.2% chance of exploitation in the next 30 days. u'SMEM partition can be manipulated in case of any compromise on HLOS, thus resulting in access to memory outside of SMEM address range which could lead to memory corruption' in Snapdragon Auto,…