###########################

# NVIDIA Driver UVMLiteController ioctl Handling Unchecked Input And Output Lengths Privilege Escalation Vulnerability

###########################

/*
Source: https://bugs.chromium.org/p/project-zero/issues/detail?id=880
 
The \\.\UVMLiteController device is created by the nvlddmkm.sys driver, and can be opened by any user. The driver handles various control codes for this device, but there is no validation for the input/output buffer and their sizes.
 
In addition to potential overreads on the input, the driver writes output directly to Irp->UserBuffer, which is the output pointer passed to DeviceIoControl() by the user. The IO control codes handled specify METHOD_BUFFERED, but the kernel does no validation that the output pointer is accessible by the user process if the user passes an output buffer size of 0.
 
This means that a user mode program can cause a write of (at least) the 32-bit values 0 or 31, or the 8-bit value 0 to any address given to the driver.
 
A PoC is attached that causes a bsod when the kernel tries to write to 0x4141414141414141+0x30.
 
 
Proof of Concept:
https://github.com/offensive-security/exploit-database-bin-sploits/raw/master/sploits/40655.zip

###########################

# Iranian Exploit DataBase = http://IeDb.Ir [2016-11-04]

###########################