VDB-99309 · CVE-2017-0329 · BID 97353

Google Android NVIDIA Boot/Power Management Processor 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.
6.1$5k-$25k0.00

Summaryinfo

A vulnerability was found in Google Android. It has been rated as critical. Affected by this issue is some unknown functionality of the component NVIDIA Boot/Power Management Processor Driver. Performing a manipulation as part of Application results in access control. This vulnerability is cataloged as CVE-2017-0329. The attack must be initiated from a local position. There is no exploit available.

Detailsinfo

A vulnerability, which was classified as critical, was found in Google Android (Smartphone Operating System) (version unknown). This affects an unknown function of the component NVIDIA Boot/Power Management Processor 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. The summary by CVE is:

An elevation of privilege vulnerability in the NVIDIA boot and power management processor driver could enable a local malicious application to execute arbitrary code within the context of the boot and power management processor. This issue is rated as High because it first requires compromising a privileged process. Product: Android. Versions: Kernel 3.18. Android ID:A-34115304. References: N-CVE-2017-0329.

The bug was discovered 04/07/2017. The weakness was shared 04/05/2017 with Qihoo 360 (Website). The advisory is shared at source.android.com. This vulnerability is uniquely identified as CVE-2017-0329 since 11/23/2016. An attack has to be approached locally. The successful exploitation requires a 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 11/27/2022). 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.

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 97353†). The entries VDB-99306, VDB-99307, VDB-99308 and VDB-99310 are related to this item. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.1
VulDB Meta Temp Score: 6.1

VulDB Base Score: 5.3
VulDB Temp Score: 5.3
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: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

11/23/2016 🔍
04/03/2017 +131 days 🔍
04/05/2017 +2 days 🔍
04/05/2017 +0 days 🔍
04/06/2017 +1 days 🔍
04/07/2017 +1 days 🔍
11/27/2022 +2060 days 🔍

Sourcesinfo

Vendor: google.com

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

CVE: CVE-2017-0329 (🔍)
GCVE (CVE): GCVE-0-2017-0329
GCVE (VulDB): GCVE-100-99309
SecurityFocus: 97353 - Google Pixel C CVE-2017-0329 Privilege Escalation Vulnerability
OSVDB: - CVE-2017-0329 - Linux - Kernel - Privilege Escalation Issue
SecurityTracker: 1038201

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

Entryinfo

Created: 04/06/2017 09:25
Updated: 11/27/2022 08:34
Changes: 04/06/2017 09:25 (60), 08/25/2020 21:52 (6), 11/27/2022 08:34 (3)
Complete: 🔍
Cache ID: 216:3F6:103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!