- 🇺🇸United States DamienMcKenna NH, USA
Should https://www.drupal.org/project/username_enumeration_prevention → be used for this?
Background: https://www.owasp.org/index.php/Testing_for_User_Enumeration_and_Guessab...(OWASP-AT-002)
First, there are two core issues that are trying to fix "user enumeration issue:
But CAS is going beyond that: Having some hints, about user names or/and emails, an attacker is able to determine which of them are CAS users by using the /user/password
form.
Don't output information about whether a user is CAS user or not. Fallback to the core behavior but fail silently on any password reset action when restrict_password_management
is TRUE
and the user is a CAS user.
TBD
TBD
None.
None.
N/A
Active
2.0
CAS
It is used for security vulnerabilities which do not need a security advisory. For example, security issues in projects which do not have security advisory coverage, or forward-porting a change already disclosed in a security advisory. See Drupal’s security advisory policy for details. Be careful publicly disclosing security vulnerabilities! Use the “Report a security vulnerability” link in the project page’s sidebar. See how to report a security issue for details.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Should https://www.drupal.org/project/username_enumeration_prevention → be used for this?