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

Talos Security Advisory for Shadowsocks-libev ss-manager (TALOS-2019-0958) #2537

Closed
CiscoTalos opened this issue Nov 8, 2019 · 5 comments
Closed
Labels

Comments

@CiscoTalos
Copy link

@CiscoTalos CiscoTalos commented Nov 8, 2019

Advisory & poc attached.

TALOS-2019-0958.zip

@madeye madeye added the duplicate label Nov 8, 2019
@madeye

This comment has been minimized.

Copy link

@madeye madeye commented Nov 8, 2019

@madeye madeye closed this in ce71f49 Nov 8, 2019
madeye added a commit that referenced this issue Nov 8, 2019
@madeye

This comment has been minimized.

Copy link

@madeye madeye commented Nov 8, 2019

The default listening path of ss-manager has been changed to ~/.ss-manager.socks.

@CiscoTalos

This comment has been minimized.

Copy link
Author

@CiscoTalos CiscoTalos commented Nov 12, 2019

Is this issue confirmed as resolved?

@CiscoTalos

This comment has been minimized.

Copy link
Author

@CiscoTalos CiscoTalos commented Nov 20, 2019

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.

@carnil

This comment has been minimized.

Copy link

@carnil carnil commented Dec 2, 2019

This appears to be CVE-2019-5164 according to the provided advisory text from #2537 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.