Windows win32k!NtUserSetInformationThread Type Confusion

The Windows Kernel is subject to a kernel-mode type-confusion vulnerability inside win32k!NtUserSetInformationThread due to referencing a user-mode handle via ObReferenceObjectByHandle with a “NULL” type specified (it should instead be using *LpcPortObjectType to protect against this vulnerability). This vulnerability can be triggered from inside CSRSS via the syscall win32k!NtUserSetInformationThread with ThreadInformationClass set to “UserThreadCsrApiPort” and the parameter of the syscall set to a HANDLE that is not an LPC object.

Leave a Reply