assetnote / kiterunner

Contextual Content Discovery Tool
GNU Affero General Public License v3.0
2.57k stars 285 forks source link

kr scan receives status code 200, however, replaying the request returns 404 #46

Open TheCodeAddiction opened 2 years ago

TheCodeAddiction commented 2 years ago

I was playing a CTF (https://tryhackme.com/room/nahamstore) and was scanning a subdomain http://marketing.nahamstore.thm/ with the following command using the routes-large.kite file from the kiterunner github page: kr scan http://nahamstore.thm/ -w ../../kiterunner/routes-large.kite 2>&1 | tee marketingLargeKiteScan.log

The scan returned a some endpoints with status code 200. However, when I replayed the attack and send it to burp, I received a 404. Screenshot_5 Screenshot_3

I used this command to replay the attack: kr kb replay -q --proxy=http://localhost:8080 -w ../../kiterunner/routes-large.kite "POST 200 [ 910, 125, 25] http://marketing.nahamstore.thm/09c2afcff60bb4dd3af7c5c5d74a482f/user/v1/add 0cf68b5253ddd70baf080aebf5430edb9f642f60"

Interestingly enough, in the CLI output it did talk about "response after redirects", however, burp doesn't seem to be redirected when I do the request and neither does my browser. Ontop of that, shouldn't kiterunner follow the redirect by default and return the correct status code? Screenshot_4

I tried blacklisting redirects from the domain http://marketing.nahamstore.thm, however, this did not help.

Is this a bug or am I using the tool wrong?

infosec-au commented 2 years ago

Hi @TheCodeAddiction - this could be a bug. We'll try and reproduce this on our side and see what's going on. Thanks for reporting it.

hijiinks1 commented 2 years ago

does somebody would be nice enough to explin to me how to install it on kali , i try to install it by git clone and the code but it didnt install it on my kali machine

TheCodeAddiction commented 2 years ago

Hi @TheCodeAddiction - this could be a bug. We'll try and reproduce this on our side and see what's going on. Thanks for reporting it.

This is still an issue, any update on the status for a fix? It makes the tool useless as the report is 100% wrong...