Page 39 of 276 results (0.004 seconds)

CVSS: 7.0EPSS: 0%CPEs: 9EXPL: 1

Windows Hyper-V Elevation of Privilege Vulnerability Vulnerabilidad de elevación de privilegios de Windows Hyper-V. • https://github.com/tandasat/CVE-2023-36427 https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-36427 •

CVSS: 5.5EPSS: 0%CPEs: 20EXPL: 0

Microsoft Local Security Authority Subsystem Service Information Disclosure Vulnerability Vulnerabilidad de divulgación de información del servicio del subsistema de la autoridad de seguridad local de Microsoft. • https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-36428 • CWE-125: Out-of-bounds Read •

CVSS: 7.8EPSS: 0%CPEs: 19EXPL: 0

Windows Installer Elevation of Privilege Vulnerability Vulnerabilidad de elevación de privilegios del instalador de Windows. • https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-36705 • CWE-59: Improper Link Resolution Before File Access ('Link Following') •

CVSS: 7.8EPSS: 0%CPEs: 20EXPL: 0

Microsoft Speech Application Programming Interface (SAPI) Elevation of Privilege Vulnerability Vulnerabilidad de elevación de privilegios de Microsoft Speech Application Programming Interface (SAPI). • https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-36719 • CWE-20: Improper Input Validation •

CVSS: 9.8EPSS: 0%CPEs: 14EXPL: 8

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. Esta falla hace que curl desborde un búfer basado en el protocolo de enlace del proxy SOCKS5. Cuando se le pide a curl que pase el nombre de host al proxy SOCKS5 para permitir que resuelva la dirección en lugar de que lo haga curl mismo, la longitud máxima que puede tener el nombre de host es 255 bytes. Si se detecta que el nombre de host es más largo, curl cambia a la resolución de nombres local y en su lugar pasa solo la dirección resuelta. • https://github.com/d0rb/CVE-2023-38545 https://github.com/vanigori/CVE-2023-38545-sample https://github.com/UTsweetyfish/CVE-2023-38545 https://github.com/fatmo666/CVE-2023-38545-libcurl-SOCKS5-heap-buffer-overflow https://github.com/imfht/CVE-2023-38545 https://github.com/bcdannyboy/CVE-2023-38545 https://github.com/dbrugman/CVE-2023-38545-POC https://github.com/Yang-Shun-Yu/CVE-2023-38545 http://seclists.org/fulldisclosure/2024/Jan/34 http://seclists.org/fulldisclosure • CWE-119: Improper Restriction of Operations within the Bounds of a Memory Buffer CWE-787: Out-of-bounds Write •