Windows 11 23H2

DATE	CVE	VULNERABILITY TITLE	RISK
2023-11-14	CVE-2023-36407	Unspecified vulnerability in Microsoft products Windows Hyper-V Elevation of Privilege Vulnerability local low complexity microsoft	7.8
2023-11-14	CVE-2023-36408	Unspecified vulnerability in Microsoft products Windows Hyper-V Elevation of Privilege Vulnerability local low complexity microsoft	7.8
2023-11-14	CVE-2023-36423	Unspecified vulnerability in Microsoft products Microsoft Remote Registry Service Remote Code Execution Vulnerability network low complexity microsoft	8.8
2023-11-14	CVE-2023-36424	Unspecified vulnerability in Microsoft products Windows Common Log File System Driver Elevation of Privilege Vulnerability local low complexity microsoft	7.8
2023-11-14	CVE-2023-36425	Unspecified vulnerability in Microsoft products Windows Distributed File System (DFS) Remote Code Execution Vulnerability network high complexity microsoft	8.0
2023-11-14	CVE-2023-36427	Unspecified vulnerability in Microsoft products Windows Hyper-V Elevation of Privilege Vulnerability local high complexity microsoft	7.0
2023-11-14	CVE-2023-36428	Unspecified vulnerability in Microsoft products Microsoft Local Security Authority Subsystem Service Information Disclosure Vulnerability local low complexity microsoft	5.5
2023-11-14	CVE-2023-36705	Unspecified vulnerability in Microsoft products Windows Installer Elevation of Privilege Vulnerability local low complexity microsoft	7.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. network low complexity haxx fedoraproject netapp microsoft CWE-787 critical	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. network low complexity haxx fedoraproject microsoft CWE-770	7.5