这是indexloc提供的服务,不要输入任何密码
Skip to content

So-called "preflight requests" for getting csrf and cookies, add pausing on some responce codes (as stop on 403 but pausing...) #845

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

Open
wants to merge 6 commits into
base: master
Choose a base branch
from

Conversation

virusvfv
Copy link

First interesting feature is so-called pre-flight requests as discussed in #525
So it can be possible to get CSRF tokens and cookies before each requests
Example:

ffuf -c -w /temp/wordlist.txt:FUZZ -u https://ffuf.io.fi/login 
     -preflight-request https://ffuf.io.fi/ 
     -capture-regex 'Set-Cookie: BruteCookie=(.*); SameSite':REGEX1
     -capture-regex 'csrftoken=(.*) blablahtml':REGEX2
     -H "Cookie: BruteCookie=REGEX1"
     -H "Foo: bar"
     -preflight-header "Cookie: BruteCookie=Empty"
     -preflight-header "FirstVisit: 1"
     -d "csrf=REGEX2&login=user&password=FUZZ"

Second feature is pausing on specified codes. For example if ffuf got 429 of 403 from WAF it can pause for some time and continue after WAF releasing.
Ex:
./ffuf -c -w /temp/wordlist.txt:FUZZ -u https://ffuf.io.fi/FUZZ -pausecode 403,429 -pausetime 60,90,120,180,300

So first pause will be 60 sec, second - 90 sec, etc. Fifth, six and other pauses will be 300 seconds.

@virusvfv virusvfv changed the title So-called "preflight requests" for getting csrf and cookies, add pausing on some responce codes (as stop ot 403 but pausing...) So-called "preflight requests" for getting csrf and cookies, add pausing on some responce codes (as stop on 403 but pausing...) Apr 25, 2025
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

Successfully merging this pull request may close these issues.

2 participants