Google Android Qualcomm Display Driver Variable access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.9 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, was found in Google Android. Affected by this vulnerability is an unknown functionality of the component Qualcomm Display Driver. Such manipulation as part of Variable leads to access control. This vulnerability is referenced as CVE-2016-5861. The attack can only be performed from a local environment. No exploit is available. It is advisable to implement a patch to correct this issue.
Details
A vulnerability was found in Google Android (Smartphone Operating System) (affected version not known). It has been rated as problematic. Affected by this issue is some unknown functionality of the component Qualcomm Display Driver. The manipulation as part of a Variable leads to a access control vulnerability. Using CWE to declare the problem leads to CWE-264. Impacted is confidentiality, integrity, and availability. CVE summarizes:
In a display driver in all Qualcomm products with Android releases from CAF using the Linux kernel, a variable controlled by userspace is used to calculate offsets and sizes for copy operations, which could result in heap overflow.
The bug was discovered 06/05/2017. The weakness was published 08/16/2017 (Website). The advisory is shared for download at source.android.com. This vulnerability is handled as CVE-2016-5861 since 06/28/2016. The attack needs to be approached locally. A simple authentication is required for exploitation. There are neither technical details nor an exploit publicly available. 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 72 days. During that time the estimated underground price was around $5k-$25k.
Applying a patch is able to eliminate this problem.
Similar entries are available at VDB-102302, VDB-102303, VDB-102304 and VDB-102305. 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.1VulDB Meta Temp Score: 6.9
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.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: Access controlCWE: CWE-264
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Partially
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: 🔍
Patch: source.codeaurora.org
Timeline
06/28/2016 🔍06/05/2017 🔍
08/16/2017 🔍
08/16/2017 🔍
08/16/2017 🔍
12/15/2022 🔍
Sources
Vendor: google.comAdvisory: source.android.com
Status: Not defined
Confirmation: 🔍
CVE: CVE-2016-5861 (🔍)
GCVE (CVE): GCVE-0-2016-5861
GCVE (VulDB): GCVE-100-105380
SecurityTracker: 1038623
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 08/16/2017 22:04Updated: 12/15/2022 19:59
Changes: 08/16/2017 22:04 (61), 11/07/2019 15:13 (2), 01/09/2021 13:24 (3), 12/15/2022 19:59 (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.