VDB-95257 · CVE-2016-8396 · BID 94712

Google Android MediaTek Video Driver information disclosure

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.
4.4$5k-$25k0.00

Summaryinfo

A vulnerability, which was classified as problematic, has been found in Google Android. This affects an unknown function of the component MediaTek Video Driver. This manipulation causes information disclosure. This vulnerability is tracked as CVE-2016-8396. The attack is restricted to local execution. No exploit exists.

Detailsinfo

A vulnerability classified as problematic was found in Google Android (Smartphone Operating System) (affected version unknown). Affected by this vulnerability is an unknown functionality of the component MediaTek Video Driver. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality. The summary by CVE is:

An information disclosure vulnerability in the MediaTek video driver could enable a local malicious application to access data outside of its permission levels. This issue is rated as High because it could be used to access sensitive data without explicit user permission. Product: Android. Versions: N/A. Android ID: A-31249105.

The bug was discovered 12/05/2016. The weakness was disclosed 01/12/2017 with Qihoo 360 (Website). The advisory is shared at securityfocus.com. This vulnerability is known as CVE-2016-8396 since 10/05/2016. An attack has to be approached locally. The successful exploitation needs a single authentication. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 07/20/2020). It is expected to see the exploit prices for this product increasing in the near future.MITRE ATT&CK project uses the attack technique T1592 for this issue.

The vulnerability was handled as a non-public zero-day exploit for at least 38 days. During that time the estimated underground price was around $5k-$25k.

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 94712†). The entries VDB-90448, VDB-90450, VDB-95213 and VDB-95214 are pretty similar. 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: 4.4
VulDB Meta Temp Score: 4.4

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

NVD Base Score: 5.5
NVD Vector: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Information disclosure
CWE: CWE-200 / CWE-284 / CWE-266
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

10/05/2016 🔍
12/05/2016 +61 days 🔍
12/05/2016 +0 days 🔍
01/12/2017 +38 days 🔍
01/12/2017 +0 days 🔍
01/13/2017 +1 days 🔍
07/20/2020 +1284 days 🔍

Sourcesinfo

Vendor: google.com

Advisory: securityfocus.com
Organization: Qihoo 360
Status: Not defined
Confirmation: 🔍

CVE: CVE-2016-8396 (🔍)
GCVE (CVE): GCVE-0-2016-8396
GCVE (VulDB): GCVE-100-95257
SecurityFocus: 94712 - Google Android CVE-2016-8396 Information Disclosure Vulnerability
OSVDB: - CVE-2016-8396 - Google - Android - Medium

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

Entryinfo

Created: 01/13/2017 08:11
Updated: 07/20/2020 17:22
Changes: 01/13/2017 08:11 (59), 07/20/2020 17:22 (7)
Complete: 🔍
Cache ID: 216:CF3:103

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you want to use VulDB in your project?

Use the official API to access entries easily!