7.8
CVE-2017-18328
- EPSS 0.04%
- Published 03.01.2019 15:29:01
- Last modified 21.11.2024 03:19:52
- Source product-security@qualcomm.com
- Teams watchlist Login
- Open Login
Use after free in QSH client rule processing in snapdragon mobile and snapdragon wear in versions MDM9206, MDM9607, MDM9635M, MDM9640, MDM9645, MDM9650, MDM9655, MSM8909W, SD 210/SD 212/SD 205, SD 425, SD 427, SD 430, SD 435, SD 450, SD 625, SD 636, SD 820, SD 835, SDA660, SDM630, SDM660, Snapdragon_High_Med_2016.
Data is provided by the National Vulnerability Database (NVD)
Qualcomm ≫ Mdm9206 Firmware Version-
Qualcomm ≫ Mdm9607 Firmware Version-
Qualcomm ≫ Mdm9635m Firmware Version-
Qualcomm ≫ Mdm9640 Firmware Version-
Qualcomm ≫ Mdm9645 Firmware Version-
Qualcomm ≫ Mdm9650 Firmware Version-
Qualcomm ≫ Mdm9655 Firmware Version-
Qualcomm ≫ Msm8909w Firmware Version-
Qualcomm ≫ Sd 210 Firmware Version-
Qualcomm ≫ Sd 212 Firmware Version-
Qualcomm ≫ Sd 205 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 820 Firmware Version-
Qualcomm ≫ Sd 835 Firmware Version-
Qualcomm ≫ Sda660 Firmware Version-
Qualcomm ≫ Sdm630 Firmware Version-
Qualcomm ≫ Sdm660 Firmware Version-
Qualcomm ≫ Snapdragon High Med 2016 Firmware Version-
Zu dieser CVE wurde keine CISA KEV oder CERT.AT-Warnung gefunden.
Type | Source | Score | Percentile |
---|---|---|---|
EPSS | FIRST.org | 0.04% | 0.096 |
Source | Base Score | Exploit Score | Impact Score | Vector string |
---|---|---|---|---|
nvd@nist.gov | 7.8 | 1.8 | 5.9 |
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/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.