Directory detection based on redirections #1062
Replies: 9 comments 2 replies
-
Hey there! Off the top of my head, the easiest fix is Setting 404 to an allowed status code probably would do it also, but dork up the rest of your scan |
Beta Was this translation helpful? Give feedback.
-
Thanks for your answer. Yeah, allowing 404 is too loud. I'll try the other option ! |
Beta Was this translation helpful? Give feedback.
-
Lmk how it goes. |
Beta Was this translation helpful? Give feedback.
-
Another option would be to rewrite the 404 for that directory to something else in burp before it hits ferox on the return trip |
Beta Was this translation helpful? Give feedback.
-
Interestingly, the result when adding "--force-recursion" is empty For the following command : feroxbuster -u http://internal.analysis.htb/ -w /opt/seclists/Discovery/Web-Content/raft-large-directories.txt --silent -d 1 | feroxbuster --stdin -o force_recursion_internal_full_cluster.txt -w /opt/seclists/Discovery/Web-Content/raft-large-files.txt -x php -d 2 --force-recursion I get he following output : ~$ cat force_recursion_internal_full_cluster.txt
403 GET 29l 93w 1284c http://internal.analysis.htb/
403 GET 29l 93w 1284c http://internal.analysis.htb/
403 GET 29l 93w 1284c http://internal.analysis.htb/ with the original command, even tho I don't list the "/users" directory, I get 82 others findings. |
Beta Was this translation helpful? Give feedback.
-
Hrm, that's interesting. Is this an active box or retired? If it's active I can take a look later. In the meantime maybe try the burp rewrite rule ? |
Beta Was this translation helpful? Give feedback.
-
thanks again, i found a bug based on this. grab a new ferox from here and lmk if it works as expected now |
Beta Was this translation helpful? Give feedback.
-
Hello @epi052 Glad it helped you finding a new bug ! I'll try as soon as possible 😉 |
Beta Was this translation helpful? Give feedback.
-
Hey ! I tested the patched version on two different applications and it's definitely better, thanks ! Will you release a new version soon ? |
Beta Was this translation helpful? Give feedback.
-
Hello,
Firstly, I apologize if the feature already exists; I couldn't find it. I am currently conducting fuzz testing on an application that includes an initial directory named "users," housing a page called "list.php."
The application behaves as follows:
However, when using Feroxbuster to scan "/users/," it follows the redirection and encounters a 404 status. Consequently, it halts fuzzing for this directory, even though the directory does exist.
Is it possible to incorporate a feature that helps detect such directories, indicating that we should continue fuzzing them?
Here is my command:
feroxbuster -u http://internal.analysis.htb/ -w /opt/seclists/Discovery/Web-Content/raft-large-directories.txt --silent -d 1 | feroxbuster --stdin -o internal_full_cluster.txt -w /opt/seclists/Discovery/Web-Content/raft-large-files.txt -x php -d 2
The options "--redirects" does not help in this setup.
Beta Was this translation helpful? Give feedback.
All reactions