CVE-2016-8812 : Detail

CVE-2016-8812

8.8
/
High
Overflow
0.07%V3
Local
2016-11-08
19h37 +00:00
2017-09-02
07h57 +00:00
CVE.org
NVD
Notifications for a CVE
Stay informed of any changes for a specific CVE.
Notifications manage

CVE Descriptions

For the NVIDIA Quadro, NVS, and GeForce products, NVIDIA GeForce Experience R340 before GFE 2.11.4.125 and R375 before GFE 3.1.0.52 contains a vulnerability in the kernel mode layer (nvstreamkms.sys) allowing a user to cause a stack buffer overflow with specially crafted executable paths, leading to a denial of service or escalation of privileges.

CVE Informations

Related Weaknesses

CWE-ID Weakness Name Source
CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data.

Metrics

Metrics Score Severity CVSS Vector Source
V3.0 8.8 HIGH CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Base: Exploitabilty Metrics

The Exploitability metrics reflect the characteristics of the thing that is vulnerable, which we refer to formally as the vulnerable component.

Attack Vector

This metric reflects the context by which vulnerability exploitation is possible.

Local

A vulnerability exploitable with Local access means that the vulnerable component is not bound to the network stack, and the attacker's path is via read/write/execute capabilities. In some cases, the attacker may be logged in locally in order to exploit the vulnerability, otherwise, she may rely on User Interaction to execute a malicious file.

Attack Complexity

This metric describes the conditions beyond the attacker's control that must exist in order to exploit the vulnerability.

Low

Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.

Privileges Required

This metric describes the level of privileges an attacker must possess before successfully exploiting the vulnerability.

Low

The attacker is authorized with (i.e. requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.

User Interaction

This metric captures the requirement for a user, other than the attacker, to participate in the successful compromise of the vulnerable component.

None

The vulnerable system can be exploited without interaction from any user.

Base: Scope Metrics

An important property captured by CVSS v3.0 is the ability for a vulnerability in one software component to impact resources beyond its means, or privileges.

Scope

Formally, Scope refers to the collection of privileges defined by a computing authority (e.g. an application, an operating system, or a sandbox environment) when granting access to computing resources (e.g. files, CPU, memory, etc). These privileges are assigned based on some method of identification and authorization. In some cases, the authorization may be simple or loosely controlled based upon predefined rules or standards. For example, in the case of Ethernet traffic sent to a network switch, the switch accepts traffic that arrives on its ports and is an authority that controls the traffic flow to other switch ports.

Changed

An exploited vulnerability can affect resources beyond the authorization privileges intended by the vulnerable component. In this case the vulnerable component and the impacted component are different.

Base: Impact Metrics

The Impact metrics refer to the properties of the impacted component.

Confidentiality Impact

This metric measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability.

High

There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.

Integrity Impact

This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information.

High

There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.

Availability Impact

This metric measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability.

High

There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Temporal Metrics

The Temporal metrics measure the current state of exploit techniques or code availability, the existence of any patches or workarounds, or the confidence that one has in the description of a vulnerability.

Environmental Metrics

 [email protected]
V2 7.2 AV:L/AC:L/Au:N/C:C/I:C/A:C [email protected]

EPSS

EPSS is a scoring model that predicts the likelihood of a vulnerability being exploited.

EPSS Score

The EPSS model produces a probability score between 0 and 1 (0 and 100%). The higher the score, the greater the probability that a vulnerability will be exploited.

EPSS Percentile

The percentile is used to rank CVE according to their EPSS score. For example, a CVE in the 95th percentile according to its EPSS score is more likely to be exploited than 95% of other CVE. Thus, the percentile is used to compare the EPSS score of a CVE with that of other CVE.
EPSS First.org

Exploit information

Exploit Database EDB-ID : 40660

Publication date : 2016-10-30 23h00 +00:00
Author : Google Security Research
EDB Verified : Yes

Source: https://bugs.chromium.org/p/project-zero/issues/detail?id=918 The NvStreamKms.sys driver calls PsSetCreateProcessNotifyRoutineEx to set up a process creation notification routine. In this particular routine, if ( cur->image_names_count > 0 ) { // info_ is the PPS_CREATE_NOTIFY_INFO that is passed to the routine. image_filename = info_->ImageFileName; buf = image_filename->Buffer; if ( buf ) { if ( !v5 ) { i = 0i64; num_chars = image_filename->Length / 2; // Look for the filename by scanning for backslash. if ( num_chars ) { while ( buf[num_chars - (unsigned int)i - 1] != '\\' ) { i = (unsigned int)(i + 1); if ( (unsigned int)i >= num_chars ) goto LABEL_39; } buf += num_chars - (unsigned __int64)(unsigned int)i; } LABEL_39: v26 = (unsigned int)i; wcscpy_s((wchar_t *)Dst, i, buf); Dst[v26] = 0; wcslwr((wchar_t *)Dst); v5 = 1; wcscpy_s is used incorrectly here, as the second argument is not the size of |Dst|, but rather the calculated size of the filename. |Dst| is a stack buffer that is at least 255 characters long. The the maximum component paths of most filesystems on Windows have a limit that is <= 255 though, so this shouldn't be an issue on normal filesystems. However, one can pass UNC paths to CreateProcessW containing forward slashes as the path delimiter, which means that the extracted filename here can be "a/b/c/...", leading to a buffer overflow. Additionally, this function has no stack cookie. e.g. CreateProcessW(L"\\\\?\\UNC\\127.0.0.1@8000\\DavWWWRoot\\..../..../..../blah.exe", ... Crashing context with my PoC (Win 10 x64 with 372.54): NvStreamKms+0x1c6a: fffff801`5c791c6a c3 ret kd> dqs rsp ffffd000`25bc5d18 00410041`00410041 kd> t ... KMODE_EXCEPTION_NOT_HANDLED (1e) ... FAULTING_IP: NvStreamKms+1c6a fffff800`5b1d1c6a c3 ret To reproduce, a WebDAV server is required (can be localhost), and the WebClient service needs to be started (start can be triggered by user without additional privileges). Then, run setup to create the long path to the target executable (you'll need to change the base directories), and then run poc_part1, and then poc_part2 (with the right UNC path) on the target machine. Proofs of Concept: https://gitlab.com/exploit-database/exploitdb-bin-sploits/-/raw/main/bin-sploits/40660.zip

Products Mentioned

Configuraton 0

Nvidia>>Geforce_experience >> Version To (including) -

Nvidia>>Geforce_910m >> Version -

Nvidia>>Geforce_920m >> Version -

Nvidia>>Geforce_920mx >> Version -

Nvidia>>Geforce_930m >> Version -

Nvidia>>Geforce_930mx >> Version -

Nvidia>>Geforce_940m >> Version -

Nvidia>>Geforce_940mx >> Version -

Nvidia>>Geforce_945m >> Version -

Nvidia>>Geforce_gt_710 >> Version -

Nvidia>>Geforce_gt_730 >> Version -

Nvidia>>Geforce_gtx_1050 >> Version -

Nvidia>>Geforce_gtx_1060 >> Version -

Nvidia>>Geforce_gtx_1070 >> Version -

Nvidia>>Geforce_gtx_1080 >> Version -

Nvidia>>Geforce_gtx_950m >> Version -

Nvidia>>Geforce_gtx_960m >> Version -

Nvidia>>Geforce_gtx_965m >> Version -

Nvidia>>Nvs_310 >> Version -

Nvidia>>Nvs_315 >> Version -

Nvidia>>Nvs_510 >> Version -

Nvidia>>Nvs_810 >> Version -

Nvidia>>Quadro_k1200 >> Version -

Nvidia>>Quadro_k420 >> Version -

Nvidia>>Quadro_k620 >> Version -

Nvidia>>Quadro_m1000m >> Version -

Nvidia>>Quadro_m2000 >> Version -

Nvidia>>Quadro_m2000m >> Version -

Nvidia>>Quadro_m3000m >> Version -

Nvidia>>Quadro_m4000 >> Version -

Nvidia>>Quadro_m4000m >> Version -

Nvidia>>Quadro_m5000 >> Version -

Nvidia>>Quadro_m5000m >> Version -

Nvidia>>Quadro_m500m >> Version -

Nvidia>>Quadro_m5500 >> Version -

Nvidia>>Quadro_m6000 >> Version -

Nvidia>>Quadro_m600m >> Version -

Nvidia>>Quadro_p5000 >> Version -

Nvidia>>Quadro_p6000 >> Version -

Nvidia>>Titan_x >> Version -

References

http://www.securityfocus.com/bid/93986
Tags : vdb-entry, x_refsource_BID
https://www.exploit-db.com/exploits/40660/
Tags : exploit, x_refsource_EXPLOIT-DB