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
exploit/windows/antivirus/ams_xfr exploit fails when cmd is unset #6888
Comments
@digininja It is a bug. Could you test the pr against your lab ? |
That fixed it. Still not getting a shell but doubt that is your fault :( |
@digininja Could you show us how to setup your lab ? |
It isn't a lab, it is on site with a client. On Wed, 18 May 2016 at 09:51 Security Corporation notifications@github.com
|
@digininja please upload a pcap to show you exploit details. |
I'll have to check with the client. Do you have a private address I can On Wed, 18 May 2016 at 10:02 Security Corporation notifications@github.com
|
This issue is considered as resolved because #6889. For the reliability issue, please go ahead and file that as a separate so we can keep track of that specifically instead of being buried in the comments here. And I hope that one is solvable because maybe getting the vuln app again for testing is tricky. Thanks. |
I've no longer got access to the app so I'll leave it for now and if I ever find it again I'll see what happens. |
Steps to reproduce
Unsetting CMD causes an error when running the exploit
This was repeatable
Expected behavior
Shouldn't get the error
Current behavior
Unset seems to change the CMD to nil where before when it wasn't set it was probably an empty string.
System stuff
Metasploit version
I installed Metasploit with:
direct from Git Master
$ ruby -v
ruby 2.3.1p112 (2016-04-26 revision 54768) [x86_64-linux]
OS
Ubuntu
The text was updated successfully, but these errors were encountered: