Qualcomm Snapdragon Mobile/Snapdragon Wear up to Snapdragon_High_Med_2016 UIM API key management
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.2 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Qualcomm Snapdragon Mobile and Snapdragon Wear and classified as problematic. This issue affects some unknown processing of the component UIM API. Performing a manipulation results in key management. This vulnerability is cataloged as CVE-2017-18319. The attack must be initiated from a local position. There is no exploit available. The affected component should be upgraded.
Details
A vulnerability, which was classified as problematic, was found in Qualcomm Snapdragon Mobile and Snapdragon Wear (Chip Software). This affects an unknown part of the component UIM API. The manipulation with an unknown input leads to a key management vulnerability. CWE is classifying the issue as CWE-320. This is going to have an impact on confidentiality. The summary by CVE is:
Information leak in UIM API debug messages in snapdragon mobile and snapdragon wear in versions MDM9206, MDM9607, MDM9615, MDM9625, MDM9635M, MDM9645, MDM9650, MDM9655, MSM8909W, SD 210/SD 212/SD 205, SD 410/12, SD 425, SD 427, SD 430, SD 435, SD 450, SD 615/16/SD 415, SD 625, SD 650/52, SD 800, SD 810, SD 820, SD 835, Snapdragon_High_Med_2016.
The bug was discovered 01/07/2019. The weakness was shared 01/03/2019 (Website). The advisory is shared at qualcomm.com. This vulnerability is uniquely identified as CVE-2017-18319 since 06/15/2018. The exploitability is told to be easy. An attack has to be approached locally. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1600.001 for this issue.
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 related to this item. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
- MDM9206
- MDM9607
- MDM9615
- MDM9625
- MDM9635M
- MDM9645
- MDM9650
- MDM9655
- MSM8909W
- SD 210-SD 212-SD 205
- SD 410-12
- SD 425
- SD 427
- SD 430
- SD 435
- SD 450
- SD 615-16-SD 415
- SD 625
- SD 650-52
- SD 800
- SD 810
- SD 820
- SD 835
- 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: 4.4VulDB Meta Temp Score: 4.3
VulDB Base Score: 3.3
VulDB Temp Score: 3.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.5
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: Key managementCWE: CWE-320
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-18319 (🔍)
GCVE (CVE): GCVE-0-2017-18319
GCVE (VulDB): GCVE-100-128649
SecurityFocus: 106128 - Qualcomm Closed-Source Components Multiple Unspecified Vulnerabilities
See also: 🔍
Entry
Created: 01/04/2019 12:04Updated: 05/04/2020 09:12
Changes: 01/04/2019 12:04 (56), 05/04/2020 09:12 (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.