Windows Message Queuing Client (MSMQC) Information Disclosure

Windows Kerberos Security Feature Bypass Vulnerability

BitLocker Security Feature Bypass Vulnerability

Microsoft Message Queuing Information Disclosure Vulnerability

Windows Message Queuing Client (MSMQC) Information Disclosure

Microsoft Message Queuing Denial of Service Vulnerability

Microsoft Message Queuing Information Disclosure Vulnerability

Microsoft Virtual Hard Disk Elevation of Privilege Vulnerability

Windows Group Policy Elevation of Privilege Vulnerability

Microsoft ODBC Driver Remote Code Execution Vulnerability

Microsoft Common Log File System Elevation of Privilege Vulnerability

Windows HTML Platforms Security Feature Bypass Vulnerability

Windows Local Session Manager (LSM) Denial of Service 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.

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.

The HTTP/2 protocol allows a denial of service (server resource consumption) because request cancellation can reset many streams quickly, as exploited in the wild in August through October 2023.

When curl retrieves an HTTP response, it stores the incoming headers so that they can be accessed later via the libcurl headers API. However, curl did not have a limit in how many or how large headers it would accept in a response, allowing a malicious server to stream an endless series of headers and eventually cause curl to run out of heap memory.

Windows GDI Elevation of Privilege Vulnerability

Windows TCP/IP Information Disclosure Vulnerability

Windows TCP/IP Denial of Service Vulnerability