Search Results (4065 CVEs found)

CVE Vendors Products Updated CVSS v3.1
CVE-2024-20681 1 Microsoft 13 Windows 10 21h2, Windows 10 21h2, Windows 10 22h2 and 10 more 2024-11-21 7.8 High
Windows Subsystem for Linux Elevation of Privilege Vulnerability
CVE-2024-20680 1 Microsoft 22 Windows 10 1507, Windows 10 1607, Windows 10 1809 and 19 more 2024-11-21 6.5 Medium
Windows Message Queuing Client (MSMQC) Information Disclosure
CVE-2024-20678 1 Microsoft 16 Windows 10 1507, Windows 10 1607, Windows 10 1809 and 13 more 2024-11-21 8.8 High
Remote Procedure Call Runtime Remote Code Execution Vulnerability
CVE-2024-20674 1 Microsoft 22 Windows 10 1507, Windows 10 1607, Windows 10 1809 and 19 more 2024-11-21 8.8 High
Windows Kerberos Security Feature Bypass Vulnerability
CVE-2024-20669 1 Microsoft 14 Windows 10 1507, Windows 10 1607, Windows 10 1809 and 11 more 2024-11-21 6.7 Medium
Secure Boot Security Feature Bypass Vulnerability
CVE-2024-20666 1 Microsoft 17 Windows 10 1507, Windows 10 1607, Windows 10 1809 and 14 more 2024-11-21 6.6 Medium
BitLocker Security Feature Bypass Vulnerability
CVE-2024-20665 1 Microsoft 14 Windows 10 1507, Windows 10 1607, Windows 10 1809 and 11 more 2024-11-21 6.1 Medium
BitLocker Security Feature Bypass Vulnerability
CVE-2024-20664 1 Microsoft 22 Windows 10 1507, Windows 10 1607, Windows 10 1809 and 19 more 2024-11-21 6.5 Medium
Microsoft Message Queuing Information Disclosure Vulnerability
CVE-2024-20663 1 Microsoft 22 Windows 10 1507, Windows 10 1607, Windows 10 1809 and 19 more 2024-11-21 6.5 Medium
Windows Message Queuing Client (MSMQC) Information Disclosure
CVE-2024-20661 1 Microsoft 22 Windows 10 1507, Windows 10 1607, Windows 10 1809 and 19 more 2024-11-21 7.5 High
Microsoft Message Queuing Denial of Service Vulnerability
CVE-2024-20660 1 Microsoft 22 Windows 10 1507, Windows 10 1607, Windows 10 1809 and 19 more 2024-11-21 6.5 Medium
Microsoft Message Queuing Information Disclosure Vulnerability
CVE-2024-20658 1 Microsoft 19 Windows 10 1507, Windows 10 1607, Windows 10 1809 and 16 more 2024-11-21 7.8 High
Microsoft Virtual Hard Disk Elevation of Privilege Vulnerability
CVE-2024-20657 1 Microsoft 22 Windows 10 1507, Windows 10 1607, Windows 10 1809 and 19 more 2024-11-21 7 High
Windows Group Policy Elevation of Privilege Vulnerability
CVE-2024-20654 1 Microsoft 22 Windows 10 1507, Windows 10 1607, Windows 10 1809 and 19 more 2024-11-21 8 High
Microsoft ODBC Driver Remote Code Execution Vulnerability
CVE-2024-20653 1 Microsoft 22 Windows 10 1507, Windows 10 1607, Windows 10 1809 and 19 more 2024-11-21 7.8 High
Microsoft Common Log File System Elevation of Privilege Vulnerability
CVE-2024-20652 1 Microsoft 21 Windows 10 1507, Windows 10 1607, Windows 10 1809 and 18 more 2024-11-21 8.1 High
Windows HTML Platforms Security Feature Bypass Vulnerability
CVE-2024-0057 2 Microsoft, Redhat 22 .net, .net Framework, Nuget and 19 more 2024-11-21 9.1 Critical
NET, .NET Framework, and Visual Studio Security Feature Bypass Vulnerability
CVE-2024-0056 2 Microsoft, Redhat 24 .net, .net Framework, System.data.sqlclient and 21 more 2024-11-21 8.7 High
Microsoft.Data.SqlClient and System.Data.SqlClient SQL Data Provider Security Feature Bypass Vulnerability
CVE-2023-44487 32 Akka, Amazon, Apache and 29 more 364 Http Server, Opensearch Data Prepper, Apisix and 361 more 2024-11-21 7.5 High
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.
CVE-2023-38545 5 Fedoraproject, Haxx, Microsoft and 2 more 19 Fedora, Libcurl, Windows 10 1809 and 16 more 2024-11-21 8.8 High
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.