Qualcomm Snapdragon Mobile up to SD 650-52 FW resource consumption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, was found in Qualcomm Snapdragon Mobile up to SD 650-52. Impacted is an unknown function of the component FW. The manipulation results in resource consumption. This vulnerability was named CVE-2018-11828. The attack may be performed from remote. There is no available exploit. You should upgrade the affected component.
Details
A vulnerability was found in Qualcomm Snapdragon Mobile up to SD 650-52 (Chip Software). It has been classified as problematic. Affected is some unknown functionality of the component FW. The manipulation with an unknown input leads to a resource consumption vulnerability. CWE is classifying the issue as CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. This is going to have an impact on availability. CVE summarizes:
When FW tries to get random mac address generated from new SW RNG and ADC values read are constant then DUT get struck in loop while trying to get random ADC samples in Snapdragon Mobile in version SD 210/SD 212/SD 205, SD 425, SD 430, SD 450, SD 625, SD 650/52
The bug was discovered 10/01/2018. The weakness was presented 10/26/2018 (Website). The advisory is shared for download at qualcomm.com. This vulnerability is traded as CVE-2018-11828 since 06/07/2018. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1499.
The vulnerability was handled as a non-public zero-day exploit for at least 25 days. During that time the estimated underground price was around $5k-$25k.
Upgrading eliminates this vulnerability.
See VDB-120497, VDB-120506, VDB-120507 and VDB-120508 for similar entries. Once again VulDB remains the best source for vulnerability data.
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: 6.4VulDB Meta Temp Score: 6.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.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: Resource consumptionCWE: CWE-400 / CWE-404
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/07/2018 🔍10/01/2018 🔍
10/26/2018 🔍
10/26/2018 🔍
10/27/2018 🔍
06/03/2023 🔍
Sources
Vendor: qualcomm.comAdvisory: qualcomm.com
Status: Not defined
Confirmation: 🔍
CVE: CVE-2018-11828 (🔍)
GCVE (CVE): GCVE-0-2018-11828
GCVE (VulDB): GCVE-100-125988
SecurityFocus: 107681
See also: 🔍
Entry
Created: 10/27/2018 18:20Updated: 06/03/2023 09:05
Changes: 10/27/2018 18:20 (59), 05/03/2020 17:15 (2), 06/03/2023 09:05 (4)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.