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

[Bug] autopwn2 server throws exception on html response - Part 2 #7415

Closed
Qubasa opened this issue Oct 8, 2016 · 2 comments · Fixed by #7417
Closed

[Bug] autopwn2 server throws exception on html response - Part 2 #7415

Qubasa opened this issue Oct 8, 2016 · 2 comments · Fixed by #7417
Assignees

Comments

@Qubasa
Copy link

Qubasa commented Oct 8, 2016

Note: This is the follow-up to my previous and now closed bug in autopwn2. #7388
The error message changed a bit the problem stays the same.

Steps to reproduce

With a clean install of metasploit development and a new .msf4 folder I started the autopwn2
module and hit run:

use auxiliary/server/browser_autopwn2
run
Starting listeners...
Time spent: 12.139677811
Using URL: http://0.0.0.0:8080/02Sz7loQOQ4YJx
Local IP: http://192.168.2.243:8080/02Sz7loQOQ4YJx
The following is a list of exploits that BrowserAutoPwn will consider using.
Exploits with the highest ranking and newest will be tried first.
...
Please use the following URL for the browser attack:
BrowserAutoPwn URL: http://192.168.2.243:8080/02Sz7loQOQ4YJx
Server started.
Starting the payload handler...
Gathering target information for 192.168.2.243
Sending HTML response to 192.168.2.243

Then I connected with my firefox browser to the given URL and this error pops up:

firefox_proto_crmfrequest - Exception handling request: uninitialized constant Rex::Exploitation::DATA_DIR

System stuff

This was on an Ubuntu machine 16.04 with a metasploit source install and the ruby version:
ruby 2.3.1p112 (2016-04-26 revision 54768) [x86_64-linux]

Metasploit version

1b06e62 Land #7414, cmd_bash fix for netbsd_mail_local

Somewhat unrelated

But whats with bug number #7390 ? I had that issue too.

@bcook-r7
Copy link
Contributor

bcook-r7 commented Oct 9, 2016

I should be able to get you going again, I see the broken commit (it's nothing that urgent to get in).

@Qubasa
Copy link
Author

Qubasa commented Oct 9, 2016

Thank you very much :)

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 a pull request may close this issue.

2 participants