Windows Bluetooth Driver Remote Code Execution Vulnerability

Win32k Elevation of Privilege Vulnerability

Internet Connection Sharing (ICS) Remote Code Execution Vulnerability

Windows MSHTML Platform Remote Code Execution Vulnerability

Windows Media Remote Code Execution Vulnerability

Bluetooth BR/EDR devices with Secure Simple Pairing and Secure Connections pairing in Bluetooth Core Specification 4.2 through 5.4 allow certain man-in-the-middle attacks that force a short key length, and might lead to discovery of the encryption key and live injection, aka BLUFFS.

Microsoft Speech Application Programming Interface (SAPI) Elevation of Privilege Vulnerability

Windows Installer Elevation of Privilege Vulnerability

Microsoft Local Security Authority Subsystem Service Information Disclosure Vulnerability

Windows Distributed File System (DFS) Remote Code Execution Vulnerability

Windows Common Log File System Driver Elevation of Privilege Vulnerability

Microsoft Remote Registry Service Remote Code Execution Vulnerability

Windows Hyper-V Elevation of Privilege Vulnerability

Windows Hyper-V Elevation of Privilege Vulnerability

Windows Hyper-V Information Disclosure Vulnerability

Windows Kernel Elevation of Privilege Vulnerability

Windows Kernel Information Disclosure Vulnerability

Windows Kernel Elevation of Privilege Vulnerability

This flaw makes curl overflow a heap based buffer in the SOCKS5 proxy handshake. When curl is asked to pass along the host name to the SOCKS5 proxy to allow that to resolve the address instead of it getting done by curl itself, the maximum length that host name can be is 255 bytes. If the host name is detected to be longer, curl switches to local name resolving and instead passes on the resolved address only. Due to this bug, the local variable that means "let the host resolve the name" could get the wrong value during a slow SOCKS5 handshake, and contrary to the intention, copy the too long host name to the target buffer instead of copying just the resolved address there. The target buffer being a heap based buffer, and the host name coming from the URL that curl has been told to operate with.

Layer 2 Tunneling Protocol Remote Code Execution Vulnerability