Owen Mccullough

A use-after-free issue exists in the Windows Ancillary Function Driver for WinSock. This allows an authorized attacker to elevate privileges locally on the system. Use-after-free is a memory corruption flaw that occurs when an application continues to use a pointer after it has been freed.

A use after free issue in the Windows Win32 Kernel Subsystem allows an authorized attacker to elevate privileges locally. Use after free is a memory corruption flaw that occurs when an application continues to use a pointer after it has been freed.

A use after free issue in the Windows Win32 Kernel Subsystem allows an authorized attacker to elevate privileges locally. Use after free is a memory corruption flaw that occurs when an application continues to use a pointer after it has been freed.

A use after free issue in the Windows Kernel allows an authorized attacker to disclose information locally. Use after free is a memory corruption flaw that occurs when an application continues to use a pointer after it has been freed.

A use after free issue exists in the Windows Ancillary Function Driver for WinSock. This flaw allows an authorized attacker to perform a local elevation of privileges. Use after free is a memory corruption flaw that occurs when an application continues to use a pointer after it has been freed.

A use after free issue exists in the Windows Ancillary Function Driver for WinSock. This allows an authorized attacker to disclose information locally. Use after free is a memory corruption flaw that occurs when an application continues to use a pointer after it has been freed.

A type confusion issue exists in the Windows Ancillary Function Driver for WinSock. This occurs when a resource is accessed using an incompatible type, which allows an authorized attacker to elevate privileges locally.

A type confusion issue occurs when a resource is accessed using an incompatible type. This flaw allows an authorized attacker to elevate privileges locally.

A type confusion issue occurs when a resource is accessed using an incompatible type. This flaw allows an authorized attacker to elevate privileges locally.

A heap-based buffer overflow in the Windows Win32 Kernel Subsystem allows an authorized attacker to elevate privileges locally. A heap-based buffer overflow occurs when a program writes more data to a heap memory buffer than it can hold, potentially leading to memory corruption.

A type confusion issue in the ICOMP component of Windows Win32K allows an authorized attacker to elevate privileges locally. Type confusion occurs when a program accesses a resource using an incompatible data type, leading to unexpected behavior.