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.
PoC: CVE-2023-38545
Simple PoC causing overflow
PoC: CVE-2023-38545
😄 CVE-2023-38545堆溢出的POC和分析文章
PoC: CVE-2023-38545-sample
Dockerfile containing all the necessary setup files to demo the exploit
PoC: NS-Project-2024-Spring
Network Security Project CVE-2023-38545
PoC: CVE-2023-38545
socks5 heap buffer overflow
PoC: CVE-2023-38545
A proof of concept for testing CVE-2023-38545 against local curl
PoC: CVE-2023-38545-POC
CVE-2023-38545 POC for the curl command line tool
PoC: CVE-2023-38545-libcurl-SOCKS5-heap-buffer-overflow
Simple PoC causing overflow
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Get alerted for CVEs like this
Register your stack and get notified within minutes when a matching CVE drops.
Start monitoring free