Vulnerabilities > CVE-2017-0317 - Incorrect Permission Assignment for Critical Resource vulnerability in Nvidia GPU Driver
Attack vector
LOCAL Attack complexity
MEDIUM Privileges required
NONE Confidentiality impact
COMPLETE Integrity impact
COMPLETE Availability impact
COMPLETE Summary
All versions of NVIDIA GPU and GeForce Experience installer contain a vulnerability where it fails to set proper permissions on the package extraction path thus allowing a non-privileged user to tamper with the extracted files, potentially leading to escalation of privileges via code execution.
Vulnerable Configurations
| Part | Description | Count |
|---|---|---|
| Application | 1 | |
| OS | 1 |
Common Weakness Enumeration (CWE)
Common Attack Pattern Enumeration and Classification (CAPEC)
- Accessing Functionality Not Properly Constrained by ACLs In applications, particularly web applications, access to functionality is mitigated by the authorization framework, whose job it is to map ACLs to elements of the application's functionality; particularly URL's for web apps. In the case that the administrator failed to specify an ACL for a particular element, an attacker may be able to access it with impunity. An attacker with the ability to access functionality not properly constrained by ACLs can obtain sensitive information and possibly compromise the entire application. Such an attacker can access resources that must be available only to users at a higher privilege level, can access management sections of the application or can run queries for data that he is otherwise not supposed to.
- Privilege Abuse An adversary is able to exploit features of the target that should be reserved for privileged users or administrators but are exposed to use by lower or non-privileged accounts. Access to sensitive information and functionality must be controlled to ensure that only authorized users are able to access these resources. If access control mechanisms are absent or misconfigured, a user may be able to access resources that are intended only for higher level users. An adversary may be able to exploit this to utilize a less trusted account to gain information and perform activities reserved for more trusted accounts. This attack differs from privilege escalation and other privilege stealing attacks in that the adversary never actually escalates their privileges but instead is able to use a lesser degree of privilege to access resources that should be (but are not) reserved for higher privilege accounts. Likewise, the adversary does not exploit trust or subvert systems - all control functionality is working as configured but the configuration does not adequately protect sensitive resources at an appropriate level.
- Directory Indexing An adversary crafts a request to a target that results in the target listing/indexing the content of a directory as output. One common method of triggering directory contents as output is to construct a request containing a path that terminates in a directory name rather than a file name since many applications are configured to provide a list of the directory's contents when such a request is received. An adversary can use this to explore the directory tree on a target as well as learn the names of files. This can often end up revealing test files, backup files, temporary files, hidden files, configuration files, user accounts, script contents, as well as naming conventions, all of which can be used by an attacker to mount additional attacks.
- Accessing, Modifying or Executing Executable Files An attack of this type exploits a system's configuration that allows an attacker to either directly access an executable file, for example through shell access; or in a possible worst case allows an attacker to upload a file and then execute it. Web servers, ftp servers, and message oriented middleware systems which have many integration points are particularly vulnerable, because both the programmers and the administrators must be in synch regarding the interfaces and the correct privileges for each interface.
- Exploiting Incorrectly Configured Access Control Security Levels An attacker exploits a weakness in the configuration of access controls and is able to bypass the intended protection that these measures guard against and thereby obtain unauthorized access to the system or network. Sensitive functionality should always be protected with access controls. However configuring all but the most trivial access control systems can be very complicated and there are many opportunities for mistakes. If an attacker can learn of incorrectly configured access security settings, they may be able to exploit this in an attack. Most commonly, attackers would take advantage of controls that provided too little protection for sensitive activities in order to perform actions that should be denied to them. In some circumstances, an attacker may be able to take advantage of overly restrictive access control policies, initiating denial of services (if an application locks because it unexpectedly failed to be granted access) or causing other legitimate actions to fail due to security. The latter class of attacks, however, is usually less severe and easier to detect than attacks based on inadequate security restrictions. This attack pattern differs from CAPEC 1, "Accessing Functionality Not Properly Constrained by ACLs" in that the latter describes attacks where sensitive functionality lacks access controls, where, in this pattern, the access control is present, but incorrectly configured.
Nessus
| NASL family | Windows |
| NASL id | NVIDIA_WIN_CVE_2017_0324.NASL |
| description | The version of the NVIDIA GPU display driver installed on the remote Windows host is 375.x prior to 376.67 or 378.x prior to 378.52. It is, therefore, affected by multiple vulnerabilities : - Multiple overflow conditions exist in the kernel mode layer handler (nvlddmkm.sys) for DxgkDdiEscape due to a failure to properly calculate the input buffer size. A local attacker can exploit these to cause a denial of service condition or the execution of arbitrary code. (CVE-2017-0308, CVE-2017-0324) - Multiple integer overflow conditions exist in the kernel mode layer handler that allow a local attacker to cause a denial of service condition or the execution of arbitrary code. (CVE-2017-0309) - A flaw exists in the kernel mode layer handler due to improper access controls that allows a local attacker to cause a denial of service condition. (CVE-2017-0310) - A flaw exists in the kernel mode layer handler due to improper access controls that allows a local attacker to cause a denial of service condition or the execution of arbitrary code. (CVE-2017-0311) - An overflow condition exists in the kernel mode layer handler for DxgDdiEscape ID 0x100008B due to improper validation of input before setting the limits for a loop. A local attacker can exploit this to cause a denial of service condition or potentially gain elevated privileges. (CVE-2017-0312) - Multiple out-of-bounds write flaws exist within the DxgkDdiSubmitCommandVirtual() function in the kernel mode layer handler due to improper validation of certain size and length values. A local attacker can exploit these to cause a denial of service condition or the execution of arbitrary code. (CVE-2017-0313, CVE-2017-0314) - A flaw exists in the kernel mode layer handler for DxgkDdiEscape due to accessing an invalid object pointer that allows a local attacker to execute arbitrary code. (CVE-2017-0315) - A flaw exists in the NVIDIA GPU and GeForce Experience Installer due to improper file permissions on the package extraction path. A local attacker can exploit this to manipulate extracted files and thereby potentially gain elevated privileges. (CVE-2017-0317) - Multiple flaws exist in the kernel mode layer handler due to improper handling of unspecified values that allow a local attacker to cause a denial of service condition. (CVE-2017-0319, CVE-2017-0320) - Multiple NULL pointer dereference flaws exist in the kernel mode layer handler due to improper validation of certain input. A local attacker can exploit these to cause a denial of service condition or potentially execute arbitrary code. (CVE-2017-0321, CVE-2017-0323) - An array-indexing error exists in the kernel mode layer handler due to improper validation of certain input. A local attacker can exploit this to cause a denial of service condition or gain elevated privileges. (CVE-2017-0322) |
| last seen | 2020-06-01 |
| modified | 2020-06-02 |
| plugin id | 97386 |
| published | 2017-02-24 |
| reporter | This script is Copyright (C) 2017-2018 Tenable Network Security, Inc. |
| source | https://www.tenable.com/plugins/nessus/97386 |
| title | NVIDIA Windows GPU Display Driver 375.x < 376.67 / 378.x < 378.52 Multiple Vulnerabilities |
| code | |