VDB-94961 · CVE-2016-8482 · BID 95231

Google Android NVIDIA GPU Driver 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.5$0-$5k0.00

Summaryinfo

A vulnerability classified as critical has been found in Google Android. This impacts an unknown function of the component NVIDIA GPU Driver. The manipulation leads to access control. This vulnerability is documented as CVE-2016-8482. The attack needs to be performed locally. There is not any exploit available. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as critical, has been found in Google Android (Smartphone Operating System) (version now known). This issue affects some unknown processing of the component NVIDIA GPU Driver. The manipulation with an unknown input 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 NVIDIA GPU driver. Product: Android. Versions: Android kernel. Android ID: A-31799863. References: N-CVE-2016-8482.

The bug was discovered 03/05/2017. The weakness was released 01/05/2017 by Di Shen with Trend Micro as Android Security Bulletin - January 2017 as confirmed advisory (Website). The advisory is shared at source.android.com. The public release was coordinated with Google. The identification of this vulnerability is CVE-2016-8482 since 10/05/2016. An attack has to be approached locally. Required for exploitation is a simple authentication. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 07/14/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 T1068 for this issue.

Upgrading eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.

The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 95231†). Entries connected to this vulnerability are available at VDB-90530, VDB-91457, VDB-92361 and VDB-94929. 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: 7.8
VulDB Meta Temp Score: 7.6

VulDB Base Score: 7.8
VulDB Temp Score: 7.5
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: No

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

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Timelineinfo

10/05/2016 🔍
01/03/2017 +90 days 🔍
01/04/2017 +1 days 🔍
01/05/2017 +1 days 🔍
01/05/2017 +0 days 🔍
03/05/2017 +59 days 🔍
04/05/2018 +396 days 🔍
07/14/2020 +831 days 🔍

Sourcesinfo

Vendor: google.com

Advisory: Android Security Bulletin - January 2017
Researcher: Di Shen
Organization: Trend Micro
Status: Confirmed
Confirmation: 🔍
Coordinated: 🔍

CVE: CVE-2016-8482 (🔍)
GCVE (CVE): GCVE-0-2016-8482
GCVE (VulDB): GCVE-100-94961
SecurityFocus: 95231 - Google Nexus NVIDIA GPU Driver Multiple Privilege Escalation Vulnerabilities
OSVDB: - CVE-2016-8482 - Google - Android - High

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

Entryinfo

Created: 01/04/2017 18:43
Updated: 07/14/2020 06:59
Changes: 01/04/2017 18:43 (66), 07/14/2020 06:59 (8)
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 ▸

Interested in the pricing of exploits?

See the underground prices here!