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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HFedora Project Fedora
OSFedoraproject37Haxx Libcurl
APPHaxx7.69.0 – 8.4.0 (bez)Microsoft Windows 10 1809
OSMicrosoft< 10.0.17763.5122Microsoft Windows 10 21h2
OSMicrosoft< 10.0.19044.3693Microsoft Windows 10 22h2
OSMicrosoft< 10.0.19045.3693Microsoft Windows 11 21h2
OSMicrosoft< 10.0.22000.2600Microsoft Windows 11 22h2
OSMicrosoft< 10.0.22621.2715Microsoft Windows 11 23h2
OSMicrosoft< 10.0.22631.2715Microsoft Windows Server 2019
OSMicrosoft< 10.0.17763.5122Microsoft Windows Server 2022
OSMicrosoft< 10.0.20348.2113Netapp Active Iq Unified Manager
APPNetappwszystkie wersjeNetapp Oncommand Insight
APPNetappwszystkie wersjeNetapp Oncommand Workflow Automation
APPNetappwszystkie wersje
Related vulnerabilities
RCE w Windows Server Update Service (WSUS) — deserializacja danych
PHP CGI argument injection – RCE na Windows przez mechanizm Best-Fit
Type Confusion w V8 (Google Chrome) — RCE przez spreparowaną stronę HTML
Type Confusion w silniku V8 Chrome — zdalne wykonanie kodu (RCE)
Use-after-free w Google Chrome Visuals umożliwiający ucieczkę z sandbox