VDB-100815 · CVE-2017-0331 · BID 98150

Google Android NVIDIA Video 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.8$25k-$100k0.00

Summaryinfo

A vulnerability, which was classified as critical, has been found in Google Android. Affected by this vulnerability is an unknown functionality of the component NVIDIA Video Driver. Performing a manipulation results in access control. This vulnerability is known as CVE-2017-0331. Attacking locally is a requirement. No exploit is available.

Detailsinfo

A vulnerability was found in Google Android (Smartphone Operating System) (affected version unknown). It has been classified as critical. This affects an unknown functionality of the component NVIDIA Video Driver. The manipulation with an unknown input 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. The summary by CVE is:

An elevation of privilege vulnerability in the NVIDIA video 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: Kernel 3.10. Android ID: A-34113000. References: N-CVE-2017-0331.

The bug was discovered 05/01/2017. The weakness was published 05/02/2017 by Security Team (Website). It is possible to read the advisory at source.android.com. This vulnerability is uniquely identified as CVE-2017-0331 since 11/23/2016. Attacking locally is a requirement. The successful exploitation needs a authentication. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $25k-$100k at the moment (estimation calculated on 09/23/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 1 days. During that time the estimated underground price was around $25k-$100k.

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 98150†). Similar entries are available at VDB-90530, VDB-91457, VDB-92361 and VDB-94958. 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.8
VulDB Meta Temp Score: 7.8

VulDB Base Score: 7.8
VulDB Temp Score: 7.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/23/2016 🔍
05/01/2017 +159 days 🔍
05/01/2017 +0 days 🔍
05/02/2017 +1 days 🔍
05/02/2017 +0 days 🔍
05/03/2017 +1 days 🔍
09/23/2020 +1239 days 🔍

Sourcesinfo

Vendor: google.com

Advisory: source.android.com
Researcher: Security Team
Status: Not defined
Confirmation: 🔍

CVE: CVE-2017-0331 (🔍)
GCVE (CVE): GCVE-0-2017-0331
GCVE (VulDB): GCVE-100-100815
SecurityFocus: 98150 - Google Nexus Nvidia Video Driver CVE-2017-0331 Privilege Escalation Vulnerability
OSVDB: - CVE-2017-0331 - Linux - Kernel - Privilege Escalation Issue

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

Entryinfo

Created: 05/03/2017 14:31
Updated: 09/23/2020 09:13
Changes: 05/03/2017 14:31 (60), 09/23/2020 09:13 (6)
Complete: 🔍
Cache ID: 216:933:103

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!