Google Android Qualcomm LED Driver Application access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.6 | $5k-$25k | 0.00 |
Summary
A vulnerability categorized as critical has been discovered in Google Android. This issue affects some unknown processing of the component Qualcomm LED Driver. Executing a manipulation as part of Application can lead to access control. This vulnerability is handled as CVE-2016-10288. It is possible to launch the attack on the local host. There is not any exploit available. It is advisable to implement a patch to correct this issue.
Details
A vulnerability classified as critical was found in Google Android (Smartphone Operating System) (affected version unknown). This vulnerability affects an unknown functionality of the component Qualcomm LED Driver. The manipulation as part of a Application leads to a access control vulnerability. The CWE definition for the vulnerability is CWE-264. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
An elevation of privilege vulnerability in the Qualcomm LED driver could enable a local malicious application to execute arbitrary code within the context of the kernel. This issue is rated as High because it first requires compromising a privileged process. Product: Android. Versions: Kernel-3.18. Android ID: A-33863909. References: QC-CR#1109763.
The bug was discovered 05/01/2017. The weakness was released 05/12/2017 (Website). The advisory is shared for download at source.android.com. This vulnerability was named CVE-2016-10288 since 03/28/2017. The attack needs to be approached locally. The successful exploitation needs a single authentication. There are neither technical details nor an exploit publicly available. The current price for an exploit might be approx. USD $5k-$25k (estimation calculated on 09/25/2020). It is expected to see the exploit prices for this product increasing in the near future.The MITRE ATT&CK project declares the attack technique as T1068.
The vulnerability was handled as a non-public zero-day exploit for at least 11 days. During that time the estimated underground price was around $25k-$100k.
Applying a patch is able to eliminate this problem.
Entries connected to this vulnerability are available at VDB-100815, VDB-101104, VDB-101105 and VDB-101106. Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
License
Website
- Vendor: https://www.google.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.9VulDB Meta Temp Score: 7.7
VulDB Base Score: 8.8
VulDB Temp Score: 8.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.0
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: Access controlCWE: CWE-264
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
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: PatchStatus: 🔍
0-Day Time: 🔍
Timeline
03/28/2017 🔍05/01/2017 🔍
05/12/2017 🔍
05/12/2017 🔍
05/13/2017 🔍
09/25/2020 🔍
Sources
Vendor: google.comAdvisory: source.android.com
Status: Not defined
Confirmation: 🔍
CVE: CVE-2016-10288 (🔍)
GCVE (CVE): GCVE-0-2016-10288
GCVE (VulDB): GCVE-100-101116
OSVDB: - CVE-2016-10288 - Google - Android - Privilege Escalation Issue
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 05/13/2017 08:49Updated: 09/25/2020 16:06
Changes: 05/13/2017 08:49 (60), 09/25/2020 16:06 (3)
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.