VDB-102515 · CVE-2017-0636 · BID 98866

Google Android MediaTek Command Queue 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.
7.6$5k-$25k0.00

Summaryinfo

A vulnerability was found in Google Android. It has been rated as critical. The affected element is an unknown function of the component MediaTek Command Queue Driver. The manipulation as part of Application leads to access control. This vulnerability is referenced as CVE-2017-0636. The attack can only be performed from a local environment. No exploit is available. To fix this issue, it is recommended to deploy a patch.

Detailsinfo

A vulnerability was found in Google Android (Smartphone Operating System) (version unknown) and classified as critical. This issue affects an unknown function of the component MediaTek Command Queue 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 command queue 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: N/A. Android ID: A-35310230. References: M-ALPS03162263.

The bug was discovered 06/01/2017. The weakness was published 06/14/2017 by Shell with Qihoo 360 (Website). It is possible to read the advisory at source.android.com. The identification of this vulnerability is CVE-2017-0636 since 11/29/2016. Attacking locally is a requirement. The successful exploitation requires a simple authentication. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 12/28/2020). It is expected to see the exploit prices for this product increasing in the near future.The attack technique deployed by this issue is T1068 according to MITRE ATT&CK.

The vulnerability was handled as a non-public zero-day exploit for at least 13 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 98866†). Similar entries are available at VDB-102302, VDB-102303, VDB-102304 and VDB-102305. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

Vendor

Name

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.9
VulDB 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: 🔍

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: Patch
Status: 🔍

0-Day Time: 🔍

Timelineinfo

11/29/2016 🔍
06/01/2017 +184 days 🔍
06/05/2017 +4 days 🔍
06/14/2017 +9 days 🔍
06/14/2017 +0 days 🔍
06/14/2017 +0 days 🔍
12/28/2020 +1293 days 🔍

Sourcesinfo

Vendor: google.com

Advisory: source.android.com
Researcher: Jake Corina, Nick Stephens (Shell)
Organization: Qihoo 360
Status: Not defined
Confirmation: 🔍

CVE: CVE-2017-0636 (🔍)
GCVE (CVE): GCVE-0-2017-0636
GCVE (VulDB): GCVE-100-102515
SecurityFocus: 98866 - Google Android MediaTek Components Multiple Privilege Escalation Vulnerabilities
SecurityTracker: 1038623

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

Entryinfo

Created: 06/14/2017 18:56
Updated: 12/28/2020 16:58
Changes: 06/14/2017 18:56 (62), 10/17/2019 22:27 (6), 12/28/2020 16:51 (3), 12/28/2020 16:58 (1)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!