VDB-101184 · CVE-2017-0615 · BID 98188

Google Android MediaTek Power 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.1$5k-$25k0.00

Summaryinfo

A vulnerability was found in Google Android. It has been declared as critical. The affected element is an unknown function of the component MediaTek Power Driver. The manipulation as part of Application results in access control. This vulnerability is cataloged as CVE-2017-0615. The attack must be initiated from a local position. There is no exploit available. Applying a patch is advised to resolve this issue.

Detailsinfo

A vulnerability was found in Google Android (Smartphone Operating System) (version now known). It has been classified as critical. Affected is some unknown processing of the component MediaTek Power Driver. The manipulation as part of a Application 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:

An elevation of privilege vulnerability in the MediaTek power 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-34259126. References: M-ALPS03150278.

The bug was discovered 05/01/2017. The weakness was shared 05/12/2017 with Qihoo 360 (Website). The advisory is shared for download at source.android.com. This vulnerability is traded as CVE-2017-0615 since 11/29/2016. The attack needs to be approached locally. Required for exploitation is a 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 12/23/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.

The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 98188†). The entries VDB-100815, VDB-101104, VDB-101105 and VDB-101106 are related to this item. VulDB is the best source for vulnerability data and more expert information about this specific topic.

Productinfo

Type

Vendor

Name

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.4
VulDB Meta Temp Score: 7.3

VulDB Base Score: 7.8
VulDB Temp Score: 7.5
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 🔍
05/01/2017 +153 days 🔍
05/01/2017 +0 days 🔍
05/12/2017 +11 days 🔍
05/12/2017 +0 days 🔍
05/13/2017 +1 days 🔍
12/23/2020 +1320 days 🔍

Sourcesinfo

Vendor: google.com

Advisory: source.android.com
Researcher: Yu Pan
Organization: Qihoo 360
Status: Not defined
Confirmation: 🔍

CVE: CVE-2017-0615 (🔍)
GCVE (CVE): GCVE-0-2017-0615
GCVE (VulDB): GCVE-100-101184
SecurityFocus: 98188
OSVDB: - CVE-2017-0615 - Google - Android - High

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

Entryinfo

Created: 05/13/2017 09:07
Updated: 12/23/2020 13:00
Changes: 05/13/2017 09:07 (61), 09/26/2020 09:23 (6), 12/23/2020 13:00 (2)
Complete: 🔍
Cache ID: 216::103

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you need the next level of professionalism?

Upgrade your account now!