2FA/MFA/OTP Bypass
Last updated
Last updated
To bypass 2FA, access the subsequent endpoint directly, knowing the path is crucial. If unsuccessful, alter the Referrer header to mimic navigation from the 2FA verification page.
Reutilizing previously used tokens for authentication within an account can be effective.
Extracting a token from one's own account to bypass 2FA in another account can be attempted.
Investigate whether the token is disclosed in a response from the web application.
Using the email verification link sent upon account creation can allow profile access without 2FA, as highlighted in a detailed .
Initiating sessions for both the user's and a victim's account, and completing 2FA for the user's account without proceeding, allows an attempt to access the next step in the victim's account flow, exploiting backend session management limitations.
Investigating the password reset function, which logs a user into the application post-reset, for its potential to allow multiple resets using the same link is crucial. Logging in with the newly reset credentials might bypass 2FA.
Compromising a user's account on a trusted OAuth platform (e.g., Google, Facebook) can offer a route to bypass 2FA.
The lack of a limit on the number of code attempts allows for brute force attacks, though potential silent rate limiting should be considered.
A slow brute force attack is viable where flow rate limits exist without an overarching rate limit.
Resending the code resets the rate limit, facilitating continued brute force attempts.
A document details techniques for bypassing client-side rate limiting.
Rate limits may protect login attempts but not internal account actions.
Excessive resending of codes via SMS incurs costs to the company, though it does not bypass 2FA.
Endless OTP generation with simple codes allows brute force by retrying a small set of codes.
Exploiting race conditions for 2FA bypass can be found in a specific document.
Exploring CSRF or Clickjacking vulnerabilities to disable 2FA is a viable strategy.
Guessing the "remember me" cookie value can bypass restrictions.
Impersonating the victim's IP address through the X-Forwarded-For header can bypass restrictions.
Testing subdomains may use outdated versions lacking 2FA support or contain vulnerable 2FA implementations.
Older API versions, indicated by /v*/ directory paths, may be vulnerable to 2FA bypass methods.
Terminating existing sessions upon 2FA activation secures accounts against unauthorized access from compromised sessions.
Immediate generation and potential unauthorized retrieval of backup codes upon 2FA activation, especially with CORS misconfigurations/XSS vulnerabilities, poses a risk.
Sensitive information disclosure (e.g., phone number) on the 2FA verification page is a concern.
A process demonstrating a potential bypass method involves account creation, 2FA activation, password reset, and subsequent login without the 2FA requirement.
Utilizing decoy requests to obfuscate brute force attempts or mislead rate limiting mechanisms adds another layer to bypass strategies. Crafting such requests requires a nuanced understanding of the application's security measures and rate limiting behaviours.
In case the OTP is created based on data the user already has or that is sending previous to create the OTP, it's possible for the user to also generate it and bypass it.
Note that even if a rate limit is in place you should try to see if the response is different when the valid OTP is sent. In , the bug hunter discovered that even if a rate limit is triggered after 20 unsuccessful attempts by responding with 401, if the valid one was sent a 200 response was received.