Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CWE-640 (忘记口令恢复机制弱) — Vulnerability Class 105

105 vulnerabilities classified as CWE-640 (忘记口令恢复机制弱). AI Chinese analysis included.

CWE-640 represents a critical authentication weakness where the password recovery process fails to adequately verify the identity of the requester. This flaw typically arises when developers implement insecure methods, such as sending passwords in plain text via email, using easily guessable security questions, or allowing unlimited reset attempts without locking mechanisms. Attackers exploit these vulnerabilities by impersonating legitimate users to bypass authentication controls, thereby gaining unauthorized access to sensitive accounts and data. To mitigate this risk, developers must enforce robust verification protocols, such as requiring multi-factor authentication or sending time-limited, cryptographically secure reset tokens to verified contact methods. By ensuring that recovery mechanisms are as secure as the initial login process, organizations can prevent account takeover attacks and maintain user trust in their security infrastructure.

MITRE CWE Description
The product contains a mechanism for users to recover or change their passwords without knowing the original password, but the mechanism is weak. 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 unau…
Common Consequences (3)
Access ControlGain Privileges or Assume Identity
An attacker could gain unauthorized access to the system by retrieving legitimate user's authentication credentials.
AvailabilityDoS: Resource Consumption (Other)
An attacker could deny service to legitimate system users by launching a brute force attack on the password recovery mechanism using user ids of legitimate users.
Integrity, OtherOther
The system's security functionality is turned against the system by the attacker.
Mitigations (5)
Architecture and DesignMake sure that all input supplied by the user to the password recovery mechanism is thoroughly filtered and validated.
Architecture and DesignDo not use standard weak security questions and use several security questions.
Architecture and DesignMake 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.
Architecture and DesignRequire 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.
Architecture and DesignNever allow the user to control what e-mail address the new password will be sent to in the password recovery mechanism.
Examples (1)
A famous example of this type of weakness being exploited is the eBay attack. eBay always displays the user id of the highest bidder. In the final minutes of the auction, one of the bidders could try to log in as the highest bidder three times. After three incorrect log in attempts, eBay password throttling would kick in and lock out the highest bidder's account for some time. An attacker could th…
CVE IDTitleCVSSSeverityPublished
CVE-2022-29174 Predictable password reset token may lead to account takeover in countly-server — countly-server 8.1 High2022-05-17
CVE-2022-24892 Multiple valid tokens for password reset in Shopware — shopware 6.4 Medium2022-04-28
CVE-2022-1073 Automatic Question Paper Generator password recovery — Automatic Question Paper Generator 7.3 High2022-03-29
CVE-2022-0777 Weak Password Recovery Mechanism for Forgotten Password in microweber/microweber — microweber/microweber 7.5 -2022-03-01
CVE-2021-27654 Pegasystems Pega 授权问题漏洞 — Pega Infinity 7.8 -2022-01-28
CVE-2022-22691 Umbraco Password Reset URL Poison — Umbraco CMS 6.8 Medium2022-01-18
CVE-2021-25961 SuiteCRM - Account Takeover in Password Reset Functionality — SuiteCRM 8.0 High2021-09-29
CVE-2021-25957 Account Takeover in "Dolibarr" via Password Reset Functionality — dolibarr 8.8 High2021-08-17
CVE-2021-37693 Re-use of email tokens in Discourse — discourse 5.3 Medium2021-08-13
CVE-2021-36804 Akaunting Password Reset Relay — Akaunting 5.4 Medium2021-08-04
CVE-2021-22763 Schneider-electric PowerLogic 多款产品授权问题漏洞 — PowerLogic PM55xx, PowerLogic PM8ECC, PowerLogic EGX100 and PowerLogic EGX300 (see security notification for version infromation) 9.8 -2021-06-11
CVE-2021-22731 Schneider Electric 授权问题漏洞 — Modicon Managed Switch MCSESM* and MCSESP* V8.21 and prior 9.8 -2021-05-26
CVE-2020-5361 Dell Client Commercial and Consumer 授权问题漏洞 — CPG BIOS 5.1 Medium2021-01-04
CVE-2019-6560 Auto-Maskin 授权问题漏洞 — Auto-Maskin RP210E Versions 3.7 and prior DCU210E Versions 3.7 and prior and Marine Observer Pro (Android App) 9.1 -2020-03-23
CVE-2018-16529 Forcepoint Email Security 授权问题漏洞 — Forcepoint Email Security 9.8 -2019-03-28

Vulnerabilities classified as CWE-640 (忘记口令恢复机制弱) represent 105 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.