Skip to content

PyZMQ vulnerable server #129

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

Merged
merged 3 commits into from
Jul 31, 2025
Merged

PyZMQ vulnerable server #129

merged 3 commits into from
Jul 31, 2025

Conversation

mr-mosi
Copy link

@mr-mosi mr-mosi commented Feb 26, 2025

@giacomo-doyensec
Copy link
Contributor

Hello @mr-mosi, thanks for your contribution!

While I was able to reproduce the issue using pyZMQ_exploit.py, I have a few suggestions to improve the testbed setup:

  • The server setup should be declared in a docker-compose file. This should be straightforward and will allow for easier reproducibility. With that in place, you can remove both setupEnv.sh and RunZmqServer.sh.
  • Please remove RunZmqExploit.sh and just document the commands to run the exploit under a Reproduction steps section in the README, together with an example payload command (could be a curl or just an echo to easily verify the issue).
  • Finally, please state explicitly that there is currently no safe version of the software. For instance, I was able to reproduce the issue on pyzmq==26.4.0 installed via pip install pyzmq.

@giacomo-doyensec
Copy link
Contributor

Hello @mr-mosi, do you have any update on this?

@mr-mosi
Copy link
Author

mr-mosi commented Apr 28, 2025

hello @giacomo-doyensec
thank you for reminding me about this PR.
the docker compose setup is ready now.

@copybara-service copybara-service bot merged commit 8b314fc into google:main Jul 31, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants