Qualcomm Snapdragon Mobile up to SD 845 Android Command Line Tool Account access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Qualcomm Snapdragon Mobile, Snapdragon Wear and Snapdragon Automobile. Affected by this vulnerability is an unknown functionality of the component Android Command Line Tool. Performing a manipulation results in access control (Account). This vulnerability is cataloged as CVE-2017-18275. The attack must be initiated from a local position. There is no exploit available.
Details
A vulnerability, which was classified as critical, was found in Qualcomm Snapdragon Mobile, Snapdragon Wear and Snapdragon Automobile (Chip Software). This affects some unknown functionality of the component Android Command Line Tool. The manipulation with an unknown input leads to a access control vulnerability (Account). CWE is classifying the issue as CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
A new account can be inserted into simContacts service using Android command line tool in Snapdragon Automobile, Snapdragon Mobile, Snapdragon Wear in MDM9206, MDM9607, MDM9650, MSM8909W, SD 210/SD 212/SD 205, SD 425, SD 430, SD 450, SD 615/16/SD 415, SD 617, SD 625, SD 650/52, SD 820, SD 820A, SD 835, SD 845.
The weakness was shared 05/06/2019. This vulnerability is uniquely identified as CVE-2017-18275 since 05/18/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. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 09/12/2023). MITRE ATT&CK project uses the attack technique T1068 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-134411, VDB-134408, VDB-134406 and VDB-134405 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
- MDM9650
- MSM8909W
- SD 205
- SD 210
- SD 212
- SD 415
- SD 425
- SD 430
- SD 450
- SD 615-16
- SD 617
- SD 625
- SD 650-52
- SD 820
- SD 820A
- SD 835
- SD 845
License
Website
- Vendor: https://www.qualcomm.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.4
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
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
Name: AccountClass: Access control / Account
CWE: CWE-284 / CWE-266
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
05/18/2018 🔍05/06/2019 🔍
05/07/2019 🔍
09/12/2023 🔍
Sources
Vendor: qualcomm.comAdvisory: qualcomm.com
Status: Not defined
CVE: CVE-2017-18275 (🔍)
GCVE (CVE): GCVE-0-2017-18275
GCVE (VulDB): GCVE-100-134409
See also: 🔍
Entry
Created: 05/07/2019 07:09Updated: 09/12/2023 15:06
Changes: 05/07/2019 07:09 (37), 06/07/2020 09:53 (18), 09/12/2023 15:06 (3)
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.