VDB-99401 · CVE-2017-0562 · BID 97345

Google Android MediaTek Touchscreen Driver Application access control

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
8.3$25k-$100k0.00

Summaryinfo

A vulnerability, which was classified as critical, has been found in Google Android. Impacted is an unknown function of the component MediaTek Touchscreen Driver. The manipulation as part of Application leads to access control. This vulnerability is documented as CVE-2017-0562. The attack needs to be performed locally. There is not any exploit available.

Detailsinfo

A vulnerability was found in Google Android (Smartphone Operating System) (affected version unknown) and classified as critical. This issue affects an unknown functionality of the component MediaTek Touchscreen Driver. The manipulation as part of a Application leads to a access control vulnerability. Using CWE to declare the problem leads to CWE-264. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

An elevation of privilege vulnerability in the MediaTek touchscreen driver could enable a local malicious application to execute arbitrary code within the context of the kernel. This issue is rated as Critical due to the possibility of a local permanent device compromise, which may require reflashing the operating system to repair the device. Product: Android. Versions: N/A. Android ID: A-30202425. References: M-ALPS02898189.

The bug was discovered 04/07/2017. The weakness was released 04/07/2017 (Website). The advisory is shared at source.android.com. The identification of this vulnerability is CVE-2017-0562 since 11/29/2016. An attack has to be approached locally. The successful exploitation needs a simple authentication. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $25k-$100k at the moment (estimation calculated on 11/27/2022). It is expected to see the exploit prices for this product increasing in the near future.MITRE ATT&CK project uses the attack technique T1068 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 97345†). Entries connected to this vulnerability are available at VDB-99354, VDB-99375, VDB-99376 and VDB-99383. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

Vendor

Name

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 8.3
VulDB Meta Temp Score: 8.3

VulDB Base Score: 8.8
VulDB Temp Score: 8.8
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 7.8
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Access control
CWE: 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-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

11/29/2016 🔍
04/03/2017 +125 days 🔍
04/07/2017 +4 days 🔍
04/07/2017 +0 days 🔍
04/07/2017 +0 days 🔍
04/08/2017 +1 days 🔍
11/27/2022 +2059 days 🔍

Sourcesinfo

Vendor: google.com

Advisory: source.android.com
Status: Not defined
Confirmation: 🔍

CVE: CVE-2017-0562 (🔍)
GCVE (CVE): GCVE-0-2017-0562
GCVE (VulDB): GCVE-100-99401
SecurityFocus: 97345 - Google Android MediaTek Touchscreen Driver CVE-2017-0562 Privilege Escalation Vulnerability
OSVDB: - CVE-2017-0562 - Google - Android - High
SecurityTracker: 1038201

scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍

Entryinfo

Created: 04/08/2017 09:45
Updated: 11/27/2022 11:56
Changes: 04/08/2017 09:45 (60), 08/26/2020 20:33 (5), 11/27/2022 11:56 (3)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to stay up to date on a daily basis?

Enable the mail alert feature now!