VDB-99307 · CVE-2017-0327 · BID 97333

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

Summaryinfo

A vulnerability was found in Google Android. It has been classified as critical. Affected is an unknown function of the component NVIDIA Crypto Driver. This manipulation as part of Application causes access control. This vulnerability is tracked as CVE-2017-0327. The attack is restricted to local execution. No exploit exists.

Detailsinfo

A vulnerability classified as critical was found in Google Android (Smartphone Operating System) (unknown version). Affected by this vulnerability is an unknown code block of the component NVIDIA Crypto Driver. The manipulation as part of a Application leads to a access control vulnerability. The CWE definition for the vulnerability is CWE-264. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

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

The bug was discovered 04/07/2017. The weakness was disclosed 04/05/2017 by Security Team (Mike) with Qihoo 360 (Website). It is possible to read the advisory at source.android.com. This vulnerability is known as CVE-2017-0327 since 11/23/2016. Attacking locally is a requirement. The requirement for exploitation is a single 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 11/27/2022). 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.

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 97333†). The entries VDB-90530, VDB-91457, VDB-92361 and VDB-94958 are pretty similar. 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.4
VulDB Meta Temp Score: 7.4

VulDB Base Score: 7.8
VulDB Temp Score: 7.8
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
Researcher: Security Team (Mike)
Organization: Qihoo 360
Status: Not defined
Confirmation: 🔍

CVE: CVE-2017-0327 (🔍)
GCVE (CVE): GCVE-0-2017-0327
GCVE (VulDB): GCVE-100-99307
SecurityFocus: 97333 - Google Android NVIDIA Crypto Driver Multiple Privilege Escalation Vulnerabilities
OSVDB: - CVE-2017-0327 - NVIDIA - Tegra Linux - Privilege Escalation Issue
SecurityTracker: 1038201

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

Entryinfo

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

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you need the next level of professionalism?

Upgrade your account now!