- Just try to access the next endpoint directly
- If this doesn't work, try to change the Referrer header as if you came from the 2FA page
2β£ Sharing Unused Code
- Check if you can get for your account a token and try to use it to bypass the 2FA in a different account.
3β£ Leaked Code
- Is the token leaked on a response from the web application?
4β£ Password Reset Function
- In almost all web applications the password reset function automatically logs the user into the application after the reset procedure is completed.
5β£ Reuse 2FA Code
- Also, try requesting multiple 2FA codes and see if previously requested Codes expire or not when a new code is requested
6β£ Brute Force
- There is any limit in the amount of codes that you can try, so you can just brute force it.
7β£ Response Manipulation
- Change failed response to success response
- Change failed status code to success status code
8β£ Rate Limit Bypass
- Using Similar Endpoints: /sign-up --> /Sign-up
- Blank char in params: code=1234%0a
- Change Origin IP using header
- Add extra params: /resetpwd?someparam=1
Dependency Confusion occurs when software installer script is tricked into pulling malicious code file from public repository.
How I found this bug?
2/ Recon π¦
1β£ I started with some Shodan recon and I found a IP that belongs to TARGET.
2β£ Using directory brute forcing tools like Dirsearch and FFUF, I found a package.json file contained all the packages which was installed in the server.
URL: /ui/package.json