forked from clowwindy/shadowsocks-libev
-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
Talos Security Advisory for Shadowsocks-libev ss-manager (TALOS-2019-0958) #2537
Labels
Comments
The default listening path of ss-manager has been changed to |
Is this issue confirmed as resolved? |
Based on the closing of this ticket and comment regarding the path change, we will consider this issue resolved on your end and prepare for public disclosure. |
This appears to be CVE-2019-5164 according to the provided advisory text from #2537 (comment) |
th3wyatt
pushed a commit
to th3wyatt/shadowsocks-libev
that referenced
this issue
Apr 8, 2020
Fix TALOS-2019-0956 (CVE-2019-5163), and TALOS-2019-0958. - [1ba753a] Fix shadowsocks#2536, TALOS-2019-0956 (CVE-2019-5163), which is a bug that IPv6 local address is not initialized when binding an IPv6 socket. - [ce71f49][748e6f3] Fix shadowsocks#2537, TALOS-2019-0958. Default listening path of ss-manager has been changed to ~/.ss-manager.socks. - [6d73201] Fix shadowsocks#2539, introduced by shadowsocks#2259.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Advisory & poc attached.
TALOS-2019-0958.zip
The text was updated successfully, but these errors were encountered: