(PC-38611)[API] fix: prevent user enumeration attack through email validation #20056
+5
−2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…lidation To prevent user enumeration attacks, the number of remaining resends must be the most probable value. Since an account should spent 99% of its life not validating their email,the max number of retries should be returned.
dnguyen-pass
force-pushed
the
PC-38611-prevent-enumeration-attack
branch
from
be34301 to
e3b2005
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
To prevent user enumeration attacks, the number of remaining resends must be the most probable value. Since an account should spent 99% of its life not validating their email,the max number of retries should be returned.
🎯 Related Ticket or 🔧 Changes Made
Ticket Jira