Weakness · High
CWE-640: Weak Password Recovery Mechanism for Forgotten Password
What it is
The product contains a mechanism for users to recover or change their passwords without knowing the original password, but the mechanism is weak.
- Severity (our rating)
- High
- Likelihood of exploit
- High
- Introduced during
- Architecture and Design, Implementation
- Exploited in the wild
- No CVE in CISA's catalog
In more detail
It is common for an application to have a mechanism that provides a means for a user to gain access to their account in the event they forget their password. Very often the password recovery mechanism is weak, which has the effect of making it more likely that it would be possible for a person other than the legitimate system user to gain access to that user's account. Weak password recovery schemes completely undermine a strong password authentication scheme. This weakness may be that the security question is too easy to guess or find an answer to (e.g. because the question is too common, or the answers can be found using social media). Or there might be an implementation weakness in the password recovery mechanism code that may for instance trick the system into e-mailing the new password to an e-mail account other than that of the user. There might be no throttling done on the rate of password resets so that a legitimate user can be denied service by an attacker if an attacker tries to recover their password in a rapid succession. The system may send the original password to the user rather than generating a new temporary password. In summary, password recovery functionality, if not carefully designed and implemented can often become the system's weakest link that can be misused in a way that would allow an attacker to gain unauthorized access to the system.
What an attacker can do
- Gain Privileges or Assume Identity (Access Control)
- DoS: Resource Consumption (Other) (Availability)
- Other (Integrity, Other)
How to prevent it
Architecture and Design
- Make sure that all input supplied by the user to the password recovery mechanism is thoroughly filtered and validated.
- Do not use standard weak security questions and use several security questions.
- Make sure that there is throttling on the number of incorrect answers to a security question. Disable the password recovery functionality after a certain (small) number of incorrect guesses.
- Require that the user properly answers the security question prior to resetting their password and sending the new password to the e-mail address of record.
- Never allow the user to control what e-mail address the new password will be sent to in the password recovery mechanism.
- Assign a new temporary password rather than revealing the original password.
H2 Security
Found it in your code?
We review where it appears, fix it with your team, and check it was not already used against you.
Talk to our teamT Academy
Stop writing it in the first place
Learn to build software and systems without weaknesses like this one, with practice on real hosts in your browser, every objective checked on the machine.
Start freeSource: MITRE Common Weakness Enumeration, CWE version 4.19.1. CWE is a trademark of The MITRE Corporation.