Google Android Nvidia TrustZone Application race condition
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.5 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical was found in Google Android. Affected by this vulnerability is an unknown functionality of the component Nvidia TrustZone. The manipulation as part of Application results in race condition. This vulnerability is cataloged as CVE-2017-6296. The attack must be initiated from a local position. There is no exploit available. A patch should be applied to remediate this issue.
Details
A vulnerability, which was classified as problematic, was found in Google Android (Smartphone Operating System) (version unknown). Affected is an unknown function of the component Nvidia TrustZone. The manipulation as part of a Application leads to a race condition vulnerability. CWE is classifying the issue as CWE-362. The product contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
"NVIDIA TrustZone Software contains a TOCTOU issue in the DRM application which may lead to the denial of service or possible escalation of privileges. This issue is rated as moderate."
The bug was discovered 02/15/2018. The weakness was shared 03/06/2018 (Website). The advisory is available at nvidia.custhelp.com. This vulnerability is traded as CVE-2017-6296 since 02/23/2017. Local access is required to approach this attack. The exploitation doesn't require any form of authentication. The technical details are unknown and an exploit is not available.
The vulnerability was handled as a non-public zero-day exploit for at least 19 days. During that time the estimated underground price was around $5k-$25k.
Applying a patch is able to eliminate this problem.
The entries VDB-114110, VDB-114111, VDB-114112 and VDB-114113 are related to this item. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Vendor
Name
License
Website
- Vendor: https://www.google.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.7VulDB Meta Temp Score: 4.7
VulDB Base Score: 2.5
VulDB Temp Score: 2.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.0
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Race conditionCWE: CWE-362
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔍
Timeline
02/23/2017 🔍02/15/2018 🔍
03/06/2018 🔍
03/06/2018 🔍
03/07/2018 🔍
01/10/2020 🔍
Sources
Vendor: google.comAdvisory: nvidia.custhelp.com
Status: Not defined
Confirmation: 🔍
CVE: CVE-2017-6296 (🔍)
GCVE (CVE): GCVE-0-2017-6296
GCVE (VulDB): GCVE-100-114114
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 03/07/2018 07:55Updated: 01/10/2020 17:27
Changes: 03/07/2018 07:55 (61), 01/10/2020 17:27 (2)
Complete: 🔍
Cache ID: 216:CFA:103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.