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

question https bruteforce #56

Open
johnjohnsp1 opened this issue Oct 23, 2024 · 4 comments
Open

question https bruteforce #56

johnjohnsp1 opened this issue Oct 23, 2024 · 4 comments

Comments

@johnjohnsp1
Copy link

Hi,
im trying to brute force the webapplication login form (https) with this command

./legba http
--username prtgadmin
--password prtgadmin
--target https://xx.xx.xx.xx
--http-method POST
--http-success-codes 200
--http-payload 'log={USERNAME}&pwd={PASSWORD}'
legba v0.9.0

[INFO ] target: https://xx.xx.xx.xx
[INFO ] username -> string 'prtgadmin'
[INFO ] password -> string 'prtgadmin'

[INFO ] runtime 1.001873666s

running on macOS apple silicon 15.0.1 sequoia
pretty sure the credentials are working, is that a good result or ?
thanks

@evilsocket
Copy link
Owner

no idea without knowing the specific web app you are targeting ... can you run that command again by adding a RUST_LOG=debug ./legba http .... and paste here the output?

@johnjohnsp1
Copy link
Author

I did update to the latest release then re issued the command as suggested

RUST_LOG=debug ./legba http --username prtgadmin --password prtgadmin --target https://172.16.4.100 --http-method POST --http-success-codes 200 --http-payload 'log={USERNAME}&pwd={PASSWORD}'
legba v0.9.0

[INFO ] target: https://172.16.4.100
[INFO ] username -> string 'prtgadmin'
[INFO ] password -> string 'prtgadmin'

[DEBUG] worker started
[DEBUG] worker started
[DEBUG] worker started
[DEBUG] worker started
[DEBUG] worker started
[DEBUG] worker started
[DEBUG] worker started
[DEBUG] worker started
[DEBUG] worker started
[DEBUG] worker started
[DEBUG] worker started
[DEBUG] worker started
[DEBUG] target=https://172.16.4.100/
[DEBUG] worker started
[DEBUG] worker started
[DEBUG] starting new connection: https://172.16.4.100/
[DEBUG] connecting to 172.16.4.100:443
[INFO ] tasks=14 mem=13.6 MiB targets=1 attempts=1 done=0 (0.00%) speed=0 reqs/s
[INFO ] tasks=14 mem=13.7 MiB targets=1 attempts=1 done=0 (0.00%) speed=0 reqs/s
[INFO ] tasks=14 mem=13.7 MiB targets=1 attempts=1 done=0 (0.00%) speed=0 reqs/s
[INFO ] tasks=14 mem=13.7 MiB targets=1 attempts=1 done=0 (0.00%) speed=0 reqs/s
[INFO ] tasks=14 mem=13.7 MiB targets=1 attempts=1 done=0 (0.00%) speed=0 reqs/s
[INFO ] tasks=14 mem=13.7 MiB targets=1 attempts=1 done=0 (0.00%) speed=0 reqs/s
[INFO ] tasks=14 mem=13.8 MiB targets=1 attempts=1 done=0 (0.00%) speed=0 reqs/s
^C[INFO ] stopping ...
[INFO ] runtime 8.016552833s

the website is the PRTG monitor networking

Screenshot 2024-12-18 alle 15 11 42

@evilsocket
Copy link
Owner

I see you interrupted with CTRL+C there, I need you to leave it running until something else such as a timeout or an error shows up.

@johnjohnsp1
Copy link
Author

here Isi the complete output from a fresh git pull to latest release

RUST_LOG=debug ./legba http --username prtgadmin --password prtgadmin --target http://172.16.4.100 --http-method POST --http-success-codes 200 --http-payload 'log={USERNAME}&pwd={PASSWORD}'
legba v0.10.0

[INFO ] target: http://172.16.4.100
[INFO ] username -> string 'prtgadmin'
[INFO ] password -> string 'prtgadmin'

[DEBUG] worker started
[DEBUG] worker started
[DEBUG] worker started
[DEBUG] worker started
[DEBUG] worker started
[DEBUG] worker started
[DEBUG] worker started
[DEBUG] worker started
[DEBUG] worker started
[DEBUG] worker started
[DEBUG] worker started
[DEBUG] worker started
[DEBUG] worker started
[DEBUG] worker started
[DEBUG] target=http://172.16.4.100/
[DEBUG] starting new connection: http://172.16.4.100/
[DEBUG] connecting to 172.16.4.100:80
[DEBUG] connected to 172.16.4.100:80
[DEBUG] flushed 271 bytes
[INFO ] tasks=14 mem=14.1 MiB targets=1 attempts=1 done=0 (0.00%) speed=0 reqs/s
[DEBUG] parsed 10 headers
[DEBUG] incoming body is content-length (54 bytes)
[DEBUG] incoming body completed
[DEBUG] redirect policy disallowed redirection to 'http://172.16.4.100/index.htm'
[DEBUG] status=302
[INFO ] runtime 2.003858333s

pretty sure the webpage is http and both credentials are working

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

No branches or pull requests

2 participants