You can, however, get round this by using Burp's session handling rules. On the face of it, this would seem to prevent the brute forcing of the verification code. The issue is that if you login using the credentials and then supply an incorrect 2FA code you are subsequently logged out and have to begin the process from the start. The scenario is that, whilst you have the username/password combination, you do not know the corresponding 2FA verification code. The objective of this particular lab is to login as the Carlos user. But for pentests it would be good to know how it would be possible to do this with dynamically generated payloads instead of a static one.
Burp suite intruder payloads how to#
I wasn't able to find a how to online and don't want to spoil me via the given solution which probably differs anyways.Īnd yes, via research on how to do this i stumbled upon a post in this forum where the support already stated that i could use the same 2FA code because it doesn't get regenerated. To invoke the makro i just make a request on the my-account page as in previous Labs before.īut how can i get a generated payload from the intruder into the makro to brute force the 2FA code.
The main problem is that i can't figure out how to pass a payload from an intruder request to the after running session-makro.Īs learned in the previous Labs, I am able to build a makro with the request-chain to first get the login page, login, submit the 2FA code and dynamically get and set the CSRF-Tokens from previous requests. I think i have the solution but the problem is i can't get it running. I am currently working on this lab: 2FA bypass using a brute-force attack.
0 kommentar(er)
