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
Support more named pipes? #10
Comments
Yeah definitely. Should be fairly simple to convert those over to this checker script. Good idea. If you're interested in taking this on go for it! I'd be happy to pull it in. If not I will be sure to get on top of this ASAP. |
Better if you do it. I don't foresee having the time. |
Eternalblue does not need a named pipe, only access to IPC$, it's the other eternals that need a named pipe to work. I can make a merge request with an updated mysmb.py with more pipe support and an improved zzz_exploit.py that does not use eternalblue but the other eternal vulnerabilities for getting a semi-interactive shell. @3ndG4me how does that sound ? |
@deus-ex-silicium you are absolutely correct. I was interested in this originally just from the scanner perspective, but this repo is so commonly used I think it's time we made some Proof-of-Concept improvements. So, in short, that all sounds great to me! I would also suggest pulling in PoCs for the other eternal exploits if you'd like. I was planning on doing that anyway as the original source (https://github.com/worawit/MS17-010) contains all the PoC exploits, but I was wanting to vet and test them first like I have with Eternal Blue (albeit zzz_exploit.py is basically all that's needed, the rest are just PoCs for controlling RIP). Either way bringing in the named pipe support and the zzz_exploit.py to use them is a good start (and a good motivator for me to add the rest in if relevant enough). |
Merged in the PR. Looks good, everything I tested worked out 👍 |
Metasploit uses the following list of named pipes:
Would it make sense to add support for all of these named pipes?
The reason I ask is because I received the following output when running
eternalblue_checker.py
:The text was updated successfully, but these errors were encountered: