From a5e179a0651e93a780f3650710abd0a6cc6e6282 Mon Sep 17 00:00:00 2001 From: Ryan Rudder <96507400+RRudder@users.noreply.github.com> Date: Mon, 15 May 2023 13:05:02 +1000 Subject: [PATCH] Updates to rec for Token is Not Invalidated After New Token is Requested --- .../recommendations.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/submissions/description/insufficient_security_configurability/weak_password_reset_implementation/token_is_not_invalidated_after_new_token_is_requested/recommendations.md b/submissions/description/insufficient_security_configurability/weak_password_reset_implementation/token_is_not_invalidated_after_new_token_is_requested/recommendations.md index a2f190b0..5b912514 100644 --- a/submissions/description/insufficient_security_configurability/weak_password_reset_implementation/token_is_not_invalidated_after_new_token_is_requested/recommendations.md +++ b/submissions/description/insufficient_security_configurability/weak_password_reset_implementation/token_is_not_invalidated_after_new_token_is_requested/recommendations.md @@ -1,11 +1,11 @@ # Recommendation(s) -The password reset token should be invalidated after each subsequent request for a password rest from a user. Overall, the password reset implementation should conform to the following guidelines: +It is best practice to invalidate old password reset tokens after each subsequent request for a password reset from a user. Overall, the password reset implementation should conform to the following guidelines: -A secure password policy should be in place for the user to create a strong new password -Password reset tokens should be long to protect against brute force guessing attacks, linked to an individual, invalidated after use, and have a short expiry time -Passwords should be stored and transmitted securely -Once a user’s password has been reset, they should be prompted to login in again through the usual login portal and not automatically signed in +- A secure password policy should be in place for the user to create a strong new password +- Password reset tokens should be long to protect against brute force guessinging attacks, linked to an individual, invalidated after use, and have a short expiry time +- Passwords should be stored and transmitted securely +- Once a user’s password has been reset, they should be prompted to login in again through the usual login portal and not automatically signed in For more information refer to the following guide relating to this vulnerability: