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

Hey guys, there's a bug when processing offsite on a custom port #17

Closed
intrd opened this Issue Apr 28, 2017 · 7 comments

Comments

Projects
None yet
2 participants
@intrd

intrd commented Apr 28, 2017

selection_739

..it falls back to port 80.

thx.

@digininja

This comment has been minimized.

Owner

digininja commented Apr 28, 2017

@intrd

This comment has been minimized.

intrd commented Apr 28, 2017

Same site..
I start from http://website.com:32914
But when it starts getting the internal urls like:

http://website.com:32914/hello-world
http://website.com:32914/hello-world2

it reverts to 80..

http://website.com:80/hello-world
http://website.com:80/hello-world2

..but is the same site!

If I start cewl without -o flag, it does not even spider those urls..

Anyway, solved the problem on iptables forwarding localhost:80 to remotesite:32914

@digininja

This comment has been minimized.

Owner

digininja commented Apr 28, 2017

@digininja

This comment has been minimized.

Owner

digininja commented Apr 30, 2017

I've reproduced the problem, trying to work out what is causing it now.

@digininja

This comment has been minimized.

Owner

digininja commented Apr 30, 2017

Found it I think, try the port_checking branch and you'll need to set a depth which doesn't really make sense when going off site but for now it is needed.

@intrd

This comment has been minimized.

intrd commented May 1, 2017

Tested here!

ruby cewl.rb http://mywebsite.com:33012/ --write port_test.txt --depth 1 -o -v

The branch "port_checking" works perfect :)

thanks @digininja

@digininja

This comment has been minimized.

Owner

digininja commented May 3, 2017

OK, I'll get the branch merged into live, thanks for confirming the fix.

@digininja digininja closed this May 3, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment