Vulnerabilities > Microsoft > Windows Server 2022 > 10.0.20348.1547
DATE | CVE | VULNERABILITY TITLE | RISK |
---|---|---|---|
2024-01-09 | CVE-2024-21307 | Race Condition vulnerability in Microsoft products Remote Desktop Client Remote Code Execution Vulnerability | 7.5 |
2024-01-09 | CVE-2024-21309 | Unspecified vulnerability in Microsoft products Windows Kernel-Mode Driver Elevation of Privilege Vulnerability | 7.8 |
2024-01-09 | CVE-2024-21311 | Unspecified vulnerability in Microsoft products Windows Cryptographic Services Information Disclosure Vulnerability | 5.5 |
2024-01-09 | CVE-2024-21313 | Unspecified vulnerability in Microsoft products Windows TCP/IP Information Disclosure Vulnerability | 5.3 |
2024-01-09 | CVE-2024-21314 | Unspecified vulnerability in Microsoft products Microsoft Message Queuing Information Disclosure Vulnerability | 6.5 |
2024-01-09 | CVE-2024-21316 | Unspecified vulnerability in Microsoft products Windows Server Key Distribution Service Security Feature Bypass | 6.1 |
2024-01-09 | CVE-2024-21320 | Unspecified vulnerability in Microsoft products Windows Themes Spoofing Vulnerability | 6.5 |
2023-11-28 | CVE-2023-24023 | 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. | 6.8 |
2023-10-18 | CVE-2023-38545 | Out-of-bounds Write vulnerability in multiple products 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. | 9.8 |
2023-09-15 | CVE-2023-38039 | Allocation of Resources Without Limits or Throttling vulnerability in multiple products 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. | 7.5 |