Show filters
1,949 Total Results
Displaying 11-20 of 1,949
Sort by:
Attacker Value
Very High

CVE-2023-28252

Disclosure Date: April 11, 2023 (last updated January 11, 2025)
Windows Common Log File System Driver Elevation of Privilege Vulnerability
Attacker Value
Very High

CVE-2022-41073

Disclosure Date: November 09, 2022 (last updated February 05, 2025)
Windows Print Spooler Elevation of Privilege Vulnerability
4
Attacker Value
Unknown

CVE-2022-34721

Disclosure Date: September 13, 2022 (last updated January 11, 2025)
Windows Internet Key Exchange (IKE) Protocol Extensions Remote Code Execution Vulnerability
Attacker Value
High

CVE-2022-26904

Disclosure Date: April 15, 2022 (last updated November 29, 2024)
Windows User Profile Service Elevation of Privilege Vulnerability
4
Attacker Value
Very High

CVE-2022-26809

Disclosure Date: April 15, 2022 (last updated November 29, 2024)
Remote Procedure Call Runtime Remote Code Execution Vulnerability
4
Attacker Value
Moderate

CVE-2022-21999

Disclosure Date: February 09, 2022 (last updated November 29, 2024)
Windows Print Spooler Elevation of Privilege Vulnerability
4
Attacker Value
High

CVE-2022-21919

Disclosure Date: January 11, 2022 (last updated November 28, 2024)
Windows User Profile Service Elevation of Privilege Vulnerability
4
Attacker Value
Unknown

CVE-2024-38134

Disclosure Date: August 13, 2024 (last updated August 16, 2024)
Kernel Streaming WOW Thunk Service Driver Elevation of Privilege Vulnerability
Attacker Value
Moderate

CVE-2024-38112

Disclosure Date: July 09, 2024 (last updated January 28, 2025)
Windows MSHTML Platform Spoofing Vulnerability
3
Attacker Value
Unknown

CVE-2023-38545

Disclosure Date: October 18, 2023 (last updated February 14, 2025)
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.