CWE-640
Weak Password Recovery Mechanism for Forgotten Password
2008-01-30
00h00 +00:00
00h00 +00:00
특정 CWE 알림
특정 CWE의 변경 사항에 대한 정보를 받아보세요.
이름: Weak Password Recovery Mechanism for Forgotten Password
The product contains a mechanism for users to recover or change their passwords without knowing the original password, but the mechanism is weak.
일반 정보
취약점 도입 방식
Architecture and Design : COMMISSION: This weakness refers to an incorrect design related to an architectural security tactic.Implementation
적용 가능한 플랫폼
언어
클래스: Not Language-Specific (Undetermined)일반적인 결과
| 범위 | 영향 | 가능성 |
|---|---|---|
| Access Control | Bypass Protection Mechanism, Gain Privileges or Assume Identity 참고: Weak password recovery schemes completely undermine a strong password authentication scheme. An attacker could gain unauthorized access to the system by retrieving a legitimate user's authentication credentials. | |
| Availability | DoS: 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 Other | Other 참고: The system's security functionality is turned against the system by the attacker. |
관찰된 예시
| 참고 자료 | 설명 |
|---|---|
CVE-2025-1570 | password reset functionality for a WordPress plugin allows a brute force attack of the one-time password |
CVE-2024-9302 | password reset functionality for a WordPress plugin allows a brute force attack of the one-time password |
CVE-2024-5277 | password recovery mechanism for AI developer toolkit does not invalidate the reset password token after it is used, allowing attackers to reuse the token to change passwords of victims |
CVE-2024-38287 | web conference product resets passwords to random 8-digit values, allowing brute force attacks by retrieving the hash |
잠재적 완화 방법
Phases : Architecture and DesignMake sure that all input supplied by the user to the password recovery mechanism is thoroughly filtered and validated.
Phases : Architecture and Design
Do not use standard weak security questions and use several security questions.
Phases : Architecture and Design
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.
Phases : Architecture and Design
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.
Phases : Architecture and Design
Never allow the user to control what e-mail address the new password will be sent to in the password recovery mechanism.
Phases : Architecture and Design
Assign a new temporary password rather than revealing the original password.
취약점 매핑 메모
근거 : This entry appears to be frequently misused for any weakness related to password changes, even though the name focuses on "Password Recovery" for a "forgotten" password.댓글 : CWE-640 should only be used when there is a "password recovery" mechanism for forgotten passwords. Consider password-related entries under CWE-1390: Weak Authentication.
관련 공격 패턴
| CAPEC ID | 공격 패턴 이름 |
|---|---|
| CAPEC-50 | Password Recovery Exploitation
An attacker may take advantage of the application feature to help users recover their forgotten passwords in order to gain access into the system with the same privileges as the original user. Generally password recovery schemes tend to be weak and insecure. |
메모
This entry might be reclassified as a category or "loose composite," since it lists multiple specific errors that can make the mechanism weak. However, under view 1000, it could be a weakness under protection mechanism failure, although it is different from most PMF issues since it is related to a feature that is designed to bypass a protection mechanism (specifically, the lack of knowledge of a password).This entry probably needs to be split; see extended description.
참고 자료
REF-44
24 Deadly Sins of Software SecurityMichael Howard, David LeBlanc, John Viega.
제출
| 이름 | 조직 | 날짜 | 출시일 | Version |
|---|---|---|---|---|
| Evgeny Lebanidze | Cigital | Draft 8 |
수정 사항
| 이름 | 조직 | 날짜 | 댓글 |
|---|---|---|---|
| CWE Content Team | MITRE | updated Common_Consequences, Description, Maintenance_Notes, Name, Relationships | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Related_Attack_Patterns | |
| CWE Content Team | MITRE | updated Taxonomy_Mappings | |
| CWE Content Team | MITRE | updated Common_Consequences | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Common_Consequences | |
| CWE Content Team | MITRE | updated References, Relationships | |
| CWE Content Team | MITRE | updated Potential_Mitigations | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Applicable_Platforms, Demonstrative_Examples, Description, Enabling_Factors_for_Exploitation, Modes_of_Introduction, Observed_Examples, Relationships | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Description | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Mapping_Notes | |
| CWE Content Team | MITRE | updated Relationships, Weakness_Ordinalities | |
| CWE Content Team | MITRE | updated Observed_Examples | |
| CWE Content Team | MITRE | updated Common_Consequences, Description, Technical_Nuance |
