NVIDIA Graphics Driver up to 341/369.58/375.62 on Quadro/NVS/GeForce Kernel Mode Layer nvlddmkm.sys DxgDdiEscape access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.1 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in NVIDIA Graphics Driver up to 341/369.58/375.62 on Quadro/NVS/GeForce. This affects the function DxgDdiEscape in the library nvlddmkm.sys of the component Kernel Mode Layer. This manipulation causes access control.
This vulnerability is tracked as CVE-2016-7381. The attack is restricted to local execution. No exploit exists.
It is recommended to upgrade the affected component.
Details
A vulnerability was found in NVIDIA Graphics Driver up to 341/369.58/375.62 on Quadro/NVS/GeForce (Hardware Driver Software). It has been declared as critical. Affected by this vulnerability is the function DxgDdiEscape in the library nvlddmkm.sys of the component Kernel Mode Layer. The manipulation with an unknown input 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:
For the NVIDIA Quadro, NVS, and GeForce products, NVIDIA Windows GPU Display Driver R340 before 342.00, R367 before 369.59, and R375 before 375.63 contains a vulnerability in the kernel mode layer (nvlddmkm.sys) handler for DxgDdiEscape where a user input to index an array is not bounds checked, leading to denial of service or potential escalation of privileges.
The weakness was disclosed 11/08/2016 (Website). The advisory is shared at nvidia.custhelp.com. This vulnerability is known as CVE-2016-7381 since 09/09/2016. The exploitation appears to be easy. An attack has to be approached locally. Required for exploitation is a single authentication. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1068 for this issue.
The vulnerability scanner Nessus provides a plugin with the ID 94576 (NVIDIA Windows GPU Display Driver 340.x / 341.x / 342.x < 342.00 / 375.x < 375.63 Multiple Vulnerabilities), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Windows and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 370263 (NVIDIA Windows GPU Local Privilege Escalation Vulnerability).
Upgrading to version 342.00, 369.59 or 375.63 eliminates this vulnerability. A possible mitigation has been published before and not just after the disclosure of the vulnerability.
The vulnerability is also documented in the databases at Tenable (94576) and SecurityFocus (BID 94172†). The entries VDB-93338, VDB-93339, VDB-93340 and VDB-93341 are pretty similar. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
- 341
- 369.0
- 369.1
- 369.2
- 369.3
- 369.4
- 369.5
- 369.6
- 369.7
- 369.8
- 369.9
- 369.10
- 369.11
- 369.12
- 369.13
- 369.14
- 369.15
- 369.16
- 369.17
- 369.18
- 369.19
- 369.20
- 369.21
- 369.22
- 369.23
- 369.24
- 369.25
- 369.26
- 369.27
- 369.28
- 369.29
- 369.30
- 369.31
- 369.32
- 369.33
- 369.34
- 369.35
- 369.36
- 369.37
- 369.38
- 369.39
- 369.40
- 369.41
- 369.42
- 369.43
- 369.44
- 369.45
- 369.46
- 369.47
- 369.48
- 369.49
- 369.50
- 369.51
- 369.52
- 369.53
- 369.54
- 369.55
- 369.56
- 369.57
- 369.58
- 375.0
- 375.1
- 375.2
- 375.3
- 375.4
- 375.5
- 375.6
- 375.7
- 375.8
- 375.9
- 375.10
- 375.11
- 375.12
- 375.13
- 375.14
- 375.15
- 375.16
- 375.17
- 375.18
- 375.19
- 375.20
- 375.21
- 375.22
- 375.23
- 375.24
- 375.25
- 375.26
- 375.27
- 375.28
- 375.29
- 375.30
- 375.31
- 375.32
- 375.33
- 375.34
- 375.35
- 375.36
- 375.37
- 375.38
- 375.39
- 375.40
- 375.41
- 375.42
- 375.43
- 375.44
- 375.45
- 375.46
- 375.47
- 375.48
- 375.49
- 375.50
- 375.51
- 375.52
- 375.53
- 375.54
- 375.55
- 375.56
- 375.57
- 375.58
- 375.59
- 375.60
- 375.61
- 375.62
License
Website
- Vendor: https://www.nvidia.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.3VulDB Meta Temp Score: 8.1
VulDB Base Score: 8.8
VulDB Temp Score: 8.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.8
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: Access controlCWE: 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-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 94576
Nessus Name: NVIDIA Windows GPU Display Driver 340.x / 341.x / 342.x < 342.00 / 375.x < 375.63 Multiple Vulnerabilities
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Graphics Driver 342.00/369.59/375.63
Timeline
09/09/2016 🔍10/19/2016 🔍
10/28/2016 🔍
11/04/2016 🔍
11/08/2016 🔍
11/08/2016 🔍
11/09/2016 🔍
09/29/2022 🔍
Sources
Vendor: nvidia.comAdvisory: nvidia.custhelp.com
Status: Not defined
Confirmation: 🔍
CVE: CVE-2016-7381 (🔍)
GCVE (CVE): GCVE-0-2016-7381
GCVE (VulDB): GCVE-100-93337
SecurityFocus: 94172 - Multiple NVIDIA Products GPU Display Driver Multiple Local Privilege Escalation Vulnerabilities
See also: 🔍
Entry
Created: 11/09/2016 08:04Updated: 09/29/2022 15:53
Changes: 11/09/2016 08:04 (50), 05/27/2019 17:37 (19), 09/29/2022 15:53 (13)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.