Google Android MediaTek Accessory Detector Driver access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as critical has been found in Google Android. This affects an unknown part of the component MediaTek Accessory Detector Driver. The manipulation results in access control. This vulnerability is cataloged as CVE-2017-0797. The attack must be initiated from a local position. There is no exploit available. It is advisable to implement a patch to correct this issue.
Details
A vulnerability, which was classified as critical, was found in Google Android (Smartphone Operating System) (the affected version unknown). Affected is an unknown part of the component MediaTek Accessory Detector Driver. The manipulation with an unknown input leads to a access control vulnerability. CWE is classifying the issue as CWE-264. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
A elevation of privilege vulnerability in the MediaTek accessory detector driver. Product: Android. Versions: Android kernel. Android ID: A-62459766. References: M-ALPS03353854.
The bug was discovered 09/05/2017. The weakness was shared 09/08/2017 with Shell (Website). The advisory is shared for download at source.android.com. This vulnerability is traded as CVE-2017-0797 since 11/29/2016. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Successful exploitation requires user interaction by the victim. 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 3 days. During that time the estimated underground price was around $25k-$100k.
Applying a patch is able to eliminate this problem.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 100652†). The entries VDB-101269, VDB-101388, VDB-101623 and VDB-106244 are related to this item. 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: 6.5VulDB Meta Temp Score: 6.4
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.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: 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
11/29/2016 🔍09/05/2017 🔍
09/05/2017 🔍
09/08/2017 🔍
09/08/2017 🔍
09/09/2017 🔍
01/11/2021 🔍
Sources
Vendor: google.comAdvisory: source.android.com
Researcher: Yu Pan, Yang Dai
Organization: Shell
Status: Not defined
Confirmation: 🔍
CVE: CVE-2017-0797 (🔍)
GCVE (CVE): GCVE-0-2017-0797
GCVE (VulDB): GCVE-100-106284
SecurityFocus: 100652 - Google Android MediaTek Components Multiple Privilege Escalation Vulnerabilities
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 09/09/2017 16:00Updated: 01/11/2021 12:48
Changes: 09/09/2017 16:00 (55), 11/14/2019 08:29 (11), 01/11/2021 12:48 (2)
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.