Vulnerability Details : CVE-2019-10583
Use after free issue occurs when camera access sensors data through direct report mode in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables in APQ8096AU, MDM9607, MSM8909W, Nicobar, QCS605, SA6155P, SDA845, SDM429W, SDM670, SDM710, SDM845, SM6150, SM8150, SM8250, SXR1130, SXR2130
Vulnerability category: Memory Corruption
Products affected by CVE-2019-10583
- cpe:2.3:o:qualcomm:mdm9607_firmware:-:*:*:*:*:*:*:*
- cpe:2.3:o:qualcomm:msm8909w_firmware:-:*:*:*:*:*:*:*
- cpe:2.3:o:qualcomm:apq8096au_firmware:-:*:*:*:*:*:*:*
- cpe:2.3:o:qualcomm:sdm845_firmware:-:*:*:*:*:*:*:*
- cpe:2.3:o:qualcomm:sdm710_firmware:-:*:*:*:*:*:*:*
- cpe:2.3:o:qualcomm:sda845_firmware:-:*:*:*:*:*:*:*
- cpe:2.3:o:qualcomm:sxr1130_firmware:-:*:*:*:*:*:*:*
- cpe:2.3:o:qualcomm:qcs605_firmware:-:*:*:*:*:*:*:*
- cpe:2.3:o:qualcomm:sm6150_firmware:-:*:*:*:*:*:*:*
- cpe:2.3:o:qualcomm:sm8150_firmware:-:*:*:*:*:*:*:*
- cpe:2.3:o:qualcomm:nicobar_firmware:-:*:*:*:*:*:*:*
- cpe:2.3:o:qualcomm:sdm670_firmware:-:*:*:*:*:*:*:*
- cpe:2.3:o:qualcomm:sm8250_firmware:-:*:*:*:*:*:*:*
- cpe:2.3:o:qualcomm:sxr2130_firmware:-:*:*:*:*:*:*:*
- cpe:2.3:o:qualcomm:sa6155p_firmware:-:*:*:*:*:*:*:*
- cpe:2.3:o:qualcomm:sdm429w_firmware:-:*:*:*:*:*:*:*
Exploit prediction scoring system (EPSS) score for CVE-2019-10583
0.04%
Probability of exploitation activity in the next 30 days
EPSS Score History
~ 10 %
Percentile, the proportion of vulnerabilities that are scored at or less
CVSS scores for CVE-2019-10583
| Base Score | Base Severity | CVSS Vector | Exploitability Score | Impact Score | Score Source | First Seen |
|---|---|---|---|---|---|---|
|
7.2
|
HIGH | AV:L/AC:L/Au:N/C:C/I:C/A:C |
3.9
|
10.0
|
NIST | |
|
7.8
|
HIGH | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
1.8
|
5.9
|
NIST |
CWE ids for CVE-2019-10583
-
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.Assigned by: nvd@nist.gov (Primary)
References for CVE-2019-10583
-
https://www.qualcomm.com/company/product-security/bulletins/january-2020-bulletin
January 2020 Security Bulletin | QualcommVendor Advisory
Jump to