Qualcomm Snapdragon Mobile/Snapdragon Wear up to Snapdragon_High_Med_2016 QSH Client Rule use after free
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Qualcomm Snapdragon Mobile and Snapdragon Wear. Affected by this issue is some unknown functionality of the component QSH Client Rule Handler. The manipulation leads to use after free. This vulnerability is uniquely identified as CVE-2017-18328. Local access is required to approach this attack. No exploit exists. It is suggested to upgrade the affected component.
Details
A vulnerability, which was classified as critical, has been found in Qualcomm Snapdragon Mobile and Snapdragon Wear (Chip Software). This issue affects an unknown code of the component QSH Client Rule Handler. The manipulation with an unknown input leads to a use after free vulnerability. Using CWE to declare the problem leads to CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
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.
The bug was discovered 01/07/2019. The weakness was disclosed 01/03/2019 (Website). The advisory is shared at qualcomm.com. The identification of this vulnerability is CVE-2017-18328 since 06/15/2018. The exploitation is known to be easy. An attack has to be approached locally. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available.
Upgrading eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 106128†). The entries VDB-120497, VDB-120506, VDB-120507 and VDB-120508 are pretty similar. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
- MDM9206
- MDM9607
- MDM9635M
- MDM9640
- MDM9645
- MDM9650
- MDM9655
- MSM8909W
- SD 205
- SD 210
- SD 212
- 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
License
Website
- Vendor: https://www.qualcomm.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.5VulDB Meta Temp Score: 6.4
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Use after freeCWE: CWE-416 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Timeline
06/15/2018 🔍12/03/2018 🔍
01/03/2019 🔍
01/03/2019 🔍
01/04/2019 🔍
01/07/2019 🔍
05/04/2020 🔍
Sources
Vendor: qualcomm.comAdvisory: qualcomm.com
Status: Not defined
Confirmation: 🔍
CVE: CVE-2017-18328 (🔍)
GCVE (CVE): GCVE-0-2017-18328
GCVE (VulDB): GCVE-100-128657
SecurityFocus: 106128 - Qualcomm Closed-Source Components Multiple Unspecified Vulnerabilities
See also: 🔍
Entry
Created: 01/04/2019 12:12Updated: 05/04/2020 09:38
Changes: 01/04/2019 12:12 (55), 05/04/2020 09:38 (9)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.