User enumeration through password reset
Cette page n'est pas encore disponible en français, sa traduction est en cours.
Si vous avez des questions ou des retours sur notre projet de traduction actuel,
n'hésitez pas à nous contacter.
Goal
Detect excessive password reset requests from an IP.
This may be caused by a malicious actor trying to use the feature to list existing users, or compromise some.
Required business logic events
Datadog auto-instruments many event types. Review your instrumented business logic events. This detection requires the following instrumented event:
Strategy
Count the number of users to which an IP requested password resets.
Require the password reset to be flagged using a user event with a usr.id metadata field set to the user receiving the password reset and a exists field set to true or false whether the user existed or not.
usr.id must be provided and unique, even if the user didn’t exist.
A Medium signal is then generated if more than 5 password resets from a single IP over 5 minutes are found for users that exist. A Low signal is generated if the user didn’t exist.
Triage and response
- Investigate the IP activity and validate that it is legitimate.
- Review your password reset process to ensure it’s not leaking whether the user existed or not.
- Consider blocking the IP to slow down the attacker.
