NVIDIA Windows GPU Display Driver Kernel Mode Layer nvlddmkm.sys DxgkDdiEscape access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in NVIDIA Windows GPU Display Driver. Affected by this vulnerability is the function DxgkDdiEscape in the library nvlddmkm.sys of the component Kernel Mode Layer. The manipulation leads to access control.
This vulnerability is documented as CVE-2017-6253. The attack needs to be performed locally. There is not any exploit available.
It is recommended to upgrade the affected component.
Details
A vulnerability was found in NVIDIA Windows GPU Display Driver (Hardware Driver Software) (version now known) and classified as critical. This issue affects the function DxgkDdiEscape in the library nvlddmkm.sys of the component Kernel Mode Layer. The manipulation with an unknown input leads to a access control vulnerability. Using CWE to declare the problem leads to CWE-264. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
NVIDIA Windows GPU Display Driver contains a vulnerability in the kernel mode layer (nvlddmkm.sys) handler for DxgkDdiEscape where the size of an input buffer is not validated which may lead to denial of service or potential escalation of privileges
The bug was discovered 07/31/2017. The weakness was released 07/28/2017 (Website). The advisory is shared at nvidia.custhelp.com. The identification of this vulnerability is CVE-2017-6253 since 02/23/2017. An attack has to be approached locally. Required for exploitation is a simple 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 102783 (NVIDIA Windows GPU Display Driver 375.x < 377.55 / 384.x < 384.94 / 385.x < 385.08 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 370484 (NVIDIA GPU Display Driver Kernel Mode Layer Handler Multiple Vulnerabilities).
Upgrading eliminates this vulnerability. A possible mitigation has been published 3 days after the disclosure of the vulnerability.
The vulnerability is also documented in the vulnerability database at Tenable (102783). Entries connected to this vulnerability are available at VDB-104619, VDB-104620, VDB-104622 and VDB-104623. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
License
Website
- Vendor: https://www.nvidia.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.5VulDB Meta Temp Score: 6.4
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
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: 102783
Nessus Name: NVIDIA Windows GPU Display Driver 375.x < 377.55 / 384.x < 384.94 / 385.x < 385.08 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: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Timeline
02/23/2017 🔍07/28/2017 🔍
07/28/2017 🔍
07/29/2017 🔍
07/31/2017 🔍
07/31/2017 🔍
08/26/2017 🔍
11/02/2019 🔍
Sources
Vendor: nvidia.comAdvisory: nvidia.custhelp.com
Status: Not defined
Confirmation: 🔍
CVE: CVE-2017-6253 (🔍)
GCVE (CVE): GCVE-0-2017-6253
GCVE (VulDB): GCVE-100-104621
See also: 🔍
Entry
Created: 07/29/2017 17:23Updated: 11/02/2019 09:41
Changes: 07/29/2017 17:23 (70), 11/02/2019 09:41 (4)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.