Reset/Forgotten Password Bypass
Last updated
Last updated
Learn & practice AWS Hacking:HackTricks Training AWS Red Team Expert (ARTE) Learn & practice GCP Hacking: HackTricks Training GCP Red Team Expert (GRTE)
Join HackenProof Discord server to communicate with experienced hackers and bug bounty hunters!
Hacking Insights Engage with content that delves into the thrill and challenges of hacking
Real-Time Hack News Keep up-to-date with fast-paced hacking world through real-time news and insights
Latest Announcements Stay informed with the newest bug bounties launching and crucial platform updates
Join us on Discord and start collaborating with top hackers today!
The HTTP referer header may leak the password reset token if it's included in the URL. This can occur when a user clicks on a third-party website link after requesting a password reset.
Impact: Potential account takeover via Cross-Site Request Forgery (CSRF) attacks.
Exploitation: To check if a password reset token is leaking in the referer header, request a password reset to your email address and click the reset link provided. Do not change your password immediately. Instead, navigate to a third-party website (like Facebook or Twitter) while intercepting the requests using Burp Suite. Inspect the requests to see if the referer header contains the password reset token, as this could expose sensitive information to third parties.
Attackers may manipulate the Host header during password reset requests to point the reset link to a malicious site.
Impact: Leads to potential account takeover by leaking reset tokens to attackers.
Mitigation Steps:
Validate the Host header against a whitelist of allowed domains.
Use secure, server-side methods to generate absolute URLs.
Patch: Use $_SERVER['SERVER_NAME'] to construct password reset URLs instead of $_SERVER['HTTP_HOST'].
References:
Attackers can manipulate the password reset request by adding additional email parameters to divert the reset link.
Add attacker email as second parameter using &
Add attacker email as second parameter using %20
Add attacker email as second parameter using |
Add attacker email as second parameter using cc
Add attacker email as second parameter using bcc
Add attacker email as second parameter using ,
Add attacker email as second parameter in json array
Mitigation Steps:
Properly parse and validate email parameters server-side.
Use prepared statements or parameterized queries to prevent injection attacks.
Attackers can modify email and password parameters in API requests to change account credentials.
Mitigation Steps:
Ensure strict parameter validation and authentication checks.
Implement robust logging and monitoring to detect and respond to suspicious activities.
Lack of rate limiting on password reset requests can lead to email bombing, overwhelming the user with reset emails.
Mitigation Steps:
Implement rate limiting based on IP address or user account.
Use CAPTCHA challenges to prevent automated abuse.
References:
Understanding the pattern or method behind token generation can lead to predicting or brute-forcing tokens. Some options:
Based Timestamp
Based on the UserID
Based on email of User
Based on Firstname and Lastname
Based on Date of Birth
Based on Cryptography
Mitigation Steps:
Use strong, cryptographic methods for token generation.
Ensure sufficient randomness and length to prevent predictability.
Tools: Use Burp Sequencer to analyze the randomness of tokens.
If UUIDs (version 1) are guessable or predictable, attackers may brute-force them to generate valid reset tokens. Check:
Mitigation Steps:
Use GUID version 4 for randomness or implement additional security measures for other versions.
Tools: Use guidtool for analyzing and generating GUIDs.
Manipulating HTTP responses to bypass error messages or restrictions.
Mitigation Steps:
Implement server-side checks to ensure response integrity.
Use secure communication channels like HTTPS to prevent man-in-the-middle attacks.
Reference:
Testing whether expired tokens can still be used for password reset.
Mitigation Steps:
Implement strict token expiration policies and validate token expiry server-side.
Attempting to brute-force the reset token using tools like Burpsuite and IP-Rotator to bypass IP-based rate limits.
Mitigation Steps:
Implement robust rate-limiting and account lockout mechanisms.
Monitor for suspicious activities indicative of brute-force attacks.
Testing if an attacker's reset token can be used in conjunction with the victim's email.
Mitigation Steps:
Ensure that tokens are bound to the user session or other user-specific attributes.
Ensuring that sessions are invalidated when a user logs out or resets their password.
Mitigation Steps:
Implement proper session management, ensuring that all sessions are invalidated upon logout or password reset.
Reset tokens should have an expiration time after which they become invalid.
Mitigation Steps:
Set a reasonable expiration time for reset tokens and strictly enforce it server-side.
Join HackenProof Discord server to communicate with experienced hackers and bug bounty hunters!
Hacking Insights Engage with content that delves into the thrill and challenges of hacking
Real-Time Hack News Keep up-to-date with fast-paced hacking world through real-time news and insights
Latest Announcements Stay informed with the newest bug bounties launching and crucial platform updates
Join us on Discord and start collaborating with top hackers today!
Learn & practice AWS Hacking:HackTricks Training AWS Red Team Expert (ARTE) Learn & practice GCP Hacking: HackTricks Training GCP Red Team Expert (GRTE)
