Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Socks5 Buffer Overflow #3737

XmiliaH opened this issue Apr 5, 2019 · 2 comments


None yet
2 participants
Copy link

commented Apr 5, 2019

I did this


I had a custom script running at 5555 which just sends [5,2] (Use Password) on first packet and on then second [5,1] (Will cause an error + return)

And got:
*** stack smashing detected ***: terminated
Or when you use a longer username:
*** buffer overflow detected ***: curl terminated

I expected the following

Curl to give an error or to truncate the password + username

curl/libcurl version

curl 7.58.0 (x86_64-pc-linux-gnu) libcurl/7.58.0 OpenSSL/1.1.0g zlib/1.2.11 libidn2/2.0.4 libpsl/0.19.1 (+libidn2/2.0.4) nghttp2/1.30.0 librtmp/2.3
Release-Date: 2018-01-24
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtmp rtsp smb smbs smtp smtps telnet tftp
Features: AsynchDNS IDN IPv6 Largefile GSS-API Kerberos SPNEGO NTLM NTLM_WB SSL libz TLS-SRP HTTP2 UnixSockets HTTPS-proxy PSL

operating system

Ubuntu 18.04.2 LTS

Problematic Codeline


This comment has been minimized.

Copy link

commented Apr 5, 2019

I cannot reproduce with that command line on 7.64.1

@bagder bagder added the crash label Apr 5, 2019


This comment has been minimized.

Copy link

commented Apr 5, 2019

Ah, I guess I need some sort of proxy running too...

bagder added a commit that referenced this issue Apr 5, 2019

socks5: make sure the data fits in the output buffer
... so that excessive user name and passwords won't overflow it.

Reported-by: XmiliaH on github
Fixes #3737

bagder added a commit that referenced this issue Apr 6, 2019

socks5: user name and passwords must be shorter than 256
bytes... since the protocol needs to store the length in a single byte field.

Reported-by: XmiliaH on github
Fixes #3737

@bagder bagder closed this in f4b6901 Apr 7, 2019

@lock lock bot locked as resolved and limited conversation to collaborators Jul 7, 2019

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.