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

Fix #4019, NameError peer in pureftpd shellshock exploit #4031

Merged
merged 1 commit into from Oct 17, 2014

Conversation

zeroSteiner
Copy link
Contributor

This fixes issue #4019 by changing #{peer}, which is not defined to #{rhost}:#{rport}.

This also explicitly disconnects in the check method to clean up.

Before:

msf-git (S:0 J:0) exploit(pureftpd_bash_env_exec) > rexploit
[*] Reloading module...

[*] Started reverse handler on 192.168.1.112:4444 
[-] Exploit failed: NameError undefined local variable or method `peer' for #<Msf::Modules::Mod6578706c6f69742f6d756c74692f6674702f70757265667470645f626173685f656e765f65786563::Metasploit4:0x0000000e7c4008>

[*] Exploit completed, but no session was created.
msf-git (S:0 J:0) exploit(pureftpd_bash_env_exec) 

After:

msf-git (S:0 J:0) exploit(pureftpd_bash_env_exec) > rexploit
[*] Reloading module...

[*] Started reverse handler on 192.168.1.112:4444 
[-] Exploit failed [bad-config]: 192.168.1.110:21 - Failed to store payload inside executable, please select a native payload
[*] Exploit completed, but no session was created.
msf-git (S:0 J:0) exploit(pureftpd_bash_env_exec) >

@zeroSteiner zeroSteiner changed the title Fix #4019, fix NameError peer in pureftpd shellshock exploit Fix #4019, NameError peer in pureftpd shellshock exploit Oct 16, 2014
@wvu wvu self-assigned this Oct 17, 2014
@wvu wvu merged commit 09069f7 into rapid7:master Oct 17, 2014
wvu added a commit that referenced this pull request Oct 17, 2014
@zeroSteiner zeroSteiner deleted the fix-4019 branch December 9, 2014 23:59
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.

None yet

2 participants