8.8
CVE-2019-2316
- EPSS 0.03%
- Published 25.07.2019 17:15:13
- Last modified 21.11.2024 04:40:41
- Source product-security@qualcomm.com
- Teams watchlist Login
- Open Login
When computing the digest a local variable is used after going out of scope in Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon Mobile, Snapdragon Voice & Music in MDM9640, QCS405, QCS605, SD 425, SD 427, SD 430, SD 435, SD 450, SD 625, SD 636, SD 665, SD 675, SD 712 / SD 710 / SD 670, SD 730, SD 845 / SD 850, SD 855, SDM660, SDX24
Data is provided by the National Vulnerability Database (NVD)
Qualcomm ≫ Mdm9640 Firmware Version-
Qualcomm ≫ Qcs405 Firmware Version-
Qualcomm ≫ Qcs605 Firmware Version-
Qualcomm ≫ Sd 425 Firmware Version-
Qualcomm ≫ Sd 427 Firmware Version-
Qualcomm ≫ Sd 430 Firmware Version-
Qualcomm ≫ Sd 435 Firmware Version-
Qualcomm ≫ Sd 450 Firmware Version-
Qualcomm ≫ Sd 625 Firmware Version-
Qualcomm ≫ Sd 636 Firmware Version-
Qualcomm ≫ Sd 665 Firmware Version-
Qualcomm ≫ Sd 675 Firmware Version-
Qualcomm ≫ Sd 712 Firmware Version-
Qualcomm ≫ Sd 710 Firmware Version-
Qualcomm ≫ Sd 670 Firmware Version-
Qualcomm ≫ Sd 730 Firmware Version-
Qualcomm ≫ Sd 845 Firmware Version-
Qualcomm ≫ Sd 850 Firmware Version-
Qualcomm ≫ Sd 855 Firmware Version-
Qualcomm ≫ Sdm660 Firmware Version-
Qualcomm ≫ Sdx24 Firmware Version-
Zu dieser CVE wurde keine CISA KEV oder CERT.AT-Warnung gefunden.
| Type | Source | Score | Percentile |
|---|---|---|---|
| EPSS | FIRST.org | 0.03% | 0.06 |
| Source | Base Score | Exploit Score | Impact Score | Vector string |
|---|---|---|---|---|
| nvd@nist.gov | 8.8 | 2 | 6 |
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
|
| nvd@nist.gov | 7.2 | 3.9 | 10 |
AV:L/AC:L/Au:N/C:C/I:C/A:C
|
CWE-416 Use After Free
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.