Search Results (Refine Search)
- Keyword (text search): cpe:2.3:o:microsoft:windows_server_2022:10.0.20348.405:*:*:*:datacenter:*:x64:*
- CPE Name Search: true
Vuln ID | Summary | CVSS Severity |
---|---|---|
CVE-2024-21320 |
Windows Themes Spoofing Vulnerability Published: January 09, 2024; 1:15:56 PM -0500 |
V4.0:(not available) V3.1: 6.5 MEDIUM V2.0:(not available) |
CVE-2024-21316 |
Windows Server Key Distribution Service Security Feature Bypass Published: January 09, 2024; 1:15:55 PM -0500 |
V4.0:(not available) V3.1: 6.1 MEDIUM V2.0:(not available) |
CVE-2024-21314 |
Microsoft Message Queuing Information Disclosure Vulnerability Published: January 09, 2024; 1:15:55 PM -0500 |
V4.0:(not available) V3.1: 6.5 MEDIUM V2.0:(not available) |
CVE-2024-21313 |
Windows TCP/IP Information Disclosure Vulnerability Published: January 09, 2024; 1:15:55 PM -0500 |
V4.0:(not available) V3.1: 5.3 MEDIUM V2.0:(not available) |
CVE-2024-21311 |
Windows Cryptographic Services Information Disclosure Vulnerability Published: January 09, 2024; 1:15:54 PM -0500 |
V4.0:(not available) V3.1: 5.5 MEDIUM V2.0:(not available) |
CVE-2024-21309 |
Windows Kernel-Mode Driver Elevation of Privilege Vulnerability Published: January 09, 2024; 1:15:54 PM -0500 |
V4.0:(not available) V3.1: 7.8 HIGH V2.0:(not available) |
CVE-2024-21307 |
Remote Desktop Client Remote Code Execution Vulnerability Published: January 09, 2024; 1:15:54 PM -0500 |
V4.0:(not available) V3.1: 7.5 HIGH V2.0:(not available) |
CVE-2024-21306 |
Microsoft Bluetooth Driver Spoofing Vulnerability Published: January 09, 2024; 1:15:54 PM -0500 |
V4.0:(not available) V3.1: 5.7 MEDIUM V2.0:(not available) |
CVE-2024-21305 |
Hypervisor-Protected Code Integrity (HVCI) Security Feature Bypass Vulnerability Published: January 09, 2024; 1:15:53 PM -0500 |
V4.0:(not available) V3.1: 4.4 MEDIUM V2.0:(not available) |
CVE-2024-20700 |
Windows Hyper-V Remote Code Execution Vulnerability Published: January 09, 2024; 1:15:53 PM -0500 |
V4.0:(not available) V3.1: 7.5 HIGH V2.0:(not available) |
CVE-2024-20698 |
Windows Kernel Elevation of Privilege Vulnerability Published: January 09, 2024; 1:15:53 PM -0500 |
V4.0:(not available) V3.1: 7.8 HIGH V2.0:(not available) |
CVE-2024-20696 |
Windows libarchive Remote Code Execution Vulnerability Published: January 09, 2024; 1:15:52 PM -0500 |
V4.0:(not available) V3.1: 7.3 HIGH V2.0:(not available) |
CVE-2024-20694 |
Windows CoreMessaging Information Disclosure Vulnerability Published: January 09, 2024; 1:15:52 PM -0500 |
V4.0:(not available) V3.1: 5.5 MEDIUM V2.0:(not available) |
CVE-2024-20692 |
Microsoft Local Security Authority Subsystem Service Information Disclosure Vulnerability Published: January 09, 2024; 1:15:52 PM -0500 |
V4.0:(not available) V3.1: 5.7 MEDIUM V2.0:(not available) |
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. Published: November 28, 2023; 2:15:41 AM -0500 |
V4.0:(not available) V3.1: 6.8 MEDIUM V2.0:(not available) |
CVE-2023-36036 |
Windows Cloud Files Mini Filter Driver Elevation of Privilege Vulnerability Published: November 14, 2023; 1:15:33 PM -0500 |
V4.0:(not available) V3.1: 7.8 HIGH V2.0:(not available) |
CVE-2023-36033 |
Windows DWM Core Library Elevation of Privilege Vulnerability Published: November 14, 2023; 1:15:32 PM -0500 |
V4.0:(not available) V3.1: 7.8 HIGH V2.0:(not available) |
CVE-2023-36025 |
Windows SmartScreen Security Feature Bypass Vulnerability Published: November 14, 2023; 1:15:31 PM -0500 |
V4.0:(not available) V3.1: 8.8 HIGH V2.0:(not available) |
CVE-2023-38545 |
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. Published: October 18, 2023; 12:15:11 AM -0400 |
V4.0:(not available) V3.1: 9.8 CRITICAL V2.0:(not available) |
CVE-2023-36584 |
Windows Mark of the Web Security Feature Bypass Vulnerability Published: October 10, 2023; 2:15:14 PM -0400 |
V4.0:(not available) V3.1: 5.4 MEDIUM V2.0:(not available) |