Qualcomm Snapdragon Automobile/Snapdragon Mobile up to SD 820A CRL Validation input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.2 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Qualcomm Snapdragon Automobile and Snapdragon Mobile up to SD 820A. It has been rated as critical. Impacted is an unknown function of the component CRL Validation. The manipulation leads to input validation. This vulnerability is listed as CVE-2017-18318. The attack may be initiated remotely. There is no available exploit. Upgrading the affected component is advised.
Details
A vulnerability, which was classified as critical, has been found in Qualcomm Snapdragon Automobile and Snapdragon Mobile up to SD 820A (Chip Software). This issue affects an unknown function of the component CRL Validation. The manipulation with an unknown input leads to a input validation vulnerability. Using CWE to declare the problem leads to CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
Missing validation check on CRL issuer name in Snapdragon Automobile, Snapdragon Mobile in versions MSM8996AU, SD 410/12, SD 425, SD 430, SD 450, SD 625, SD 650/52, SD 810, SD 820, SD 820A.
The bug was discovered 11/05/2018. The weakness was presented 11/28/2018 (Website). The advisory is shared at qualcomm.com. The identification of this vulnerability is CVE-2017-18318 since 06/15/2018. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available.
The vulnerability was handled as a non-public zero-day exploit for at least 23 days. During that time the estimated underground price was around $5k-$25k.
Upgrading eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 105838†). See VDB-120497, VDB-120506, VDB-120507 and VDB-120508 for similar entries. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.qualcomm.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.4
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.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: Input validationCWE: CWE-20
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
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 🔍11/05/2018 🔍
11/05/2018 🔍
11/28/2018 🔍
11/28/2018 🔍
11/29/2018 🔍
05/03/2020 🔍
Sources
Vendor: qualcomm.comAdvisory: qualcomm.com
Status: Not defined
Confirmation: 🔍
CVE: CVE-2017-18318 (🔍)
GCVE (CVE): GCVE-0-2017-18318
GCVE (VulDB): GCVE-100-127253
SecurityFocus: 105838 - Qualcomm Closed-Source Components Multiple Unspecified Vulnerabilities
See also: 🔍
Entry
Created: 11/29/2018 07:39Updated: 05/03/2020 21:48
Changes: 11/29/2018 07:39 (61), 05/03/2020 21:48 (4)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.