Add CAPTCHA verification, rate limiting, and dummy resetRequest cookie to mitigate automation and username enumeration in security question handler. #1601
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
The Vulnerability Description:
The handler endpoint accepted an email from the query string and looked up security questions without requiring a CAPTCHA, allowing attackers to automate requests and probe the system. When no record was found, it returned a blank response, inadvertently exposing which emails were registered and enabling user enumeration.
This Fix:
The patch enforces an anti-automation CAPTCHA check, adds basic IP-based rate limiting, and returns a dummy ‘resetRequest’ cookie even when the email is not found, preventing attackers from distinguishing valid emails from invalid ones.
The Cause of the Issue:
The handler failed to verify that the requester was a human (no CAPTCHA), did not limit repeated attempts from the same IP, and exposed user registration status through different responses based on email presence.
The Patch Implementation:
The changes add a CAPTCHA validation and a rate limiter at the start of the handler. Both legitimate and invalid requests now receive a ‘resetRequest’ cookie, ensuring consistent responses and thwarting enumeration and automation attacks.
Vulnerability Details
Code Snippets
How to Modify the Patch
You can modify this patch by using one of the two methods outlined below. We recommend using the
@zeropath-ai-devbot for updating the code. If you encounter any bugs or issues with the patch, please report them here.Ask
@zeropath-ai-dev!To request modifications, please post a comment beginning with
@zeropath-ai-devand specify the changes required.@zeropath-ai-devwill then implement the requested adjustments and commit them to the specified branch in this pull request. Our bot is capable of managing changes across multiple files and various development-related requests.Manually Modify the Files