Tên: 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.

Thông tin chung

Các cách xuất hiện

Architecture and Design : COMMISSION: This weakness refers to an incorrect design related to an architectural security tactic.
Implementation

Nền tảng áp dụng

Ngôn ngữ

Lớp: Not Language-Specific (Undetermined)

Hậu quả phổ biến

Phạm vi	Tác động	Khả năng xảy ra
Access Control	Bypass Protection Mechanism, Gain Privileges or Assume Identity Ghi chú: 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) Ghi chú: 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 Ghi chú: The system's security functionality is turned against the system by the attacker.

Ví dụ đã quan sát

Tài liệu tham khảo	Mô tả
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

Các biện pháp giảm thiểu tiềm năng

Phases : Architecture and Design
Make 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.

Ghi chú ánh xạ lỗ hổng

Lý do : 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.
Bình luận : 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.

Mẫu tấn công liên quan

ID CAPEC	Tên mẫu tấn công
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.

Ghi chú

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.

Tài liệu tham khảo

REF-44

24 Deadly Sins of Software Security
Michael Howard, David LeBlanc, John Viega.

Gửi

Tên	Tổ chức	Ngày	Ngày phát hành	Version
Evgeny Lebanidze	Cigital	2008-01-30 +00:00	2008-01-30 +00:00	Draft 8

Sửa đổi

Tên	Tổ chức	Ngày	Bình luận
CWE Content Team	MITRE	2008-09-08 +00:00	updated Common_Consequences, Description, Maintenance_Notes, Name, Relationships
CWE Content Team	MITRE	2009-03-10 +00:00	updated Relationships
CWE Content Team	MITRE	2009-05-27 +00:00	updated Related_Attack_Patterns
CWE Content Team	MITRE	2010-02-16 +00:00	updated Taxonomy_Mappings
CWE Content Team	MITRE	2010-12-13 +00:00	updated Common_Consequences
CWE Content Team	MITRE	2011-03-29 +00:00	updated Relationships
CWE Content Team	MITRE	2011-06-01 +00:00	updated Common_Consequences
CWE Content Team	MITRE	2012-05-11 +00:00	updated References, Relationships
CWE Content Team	MITRE	2012-10-30 +00:00	updated Potential_Mitigations
CWE Content Team	MITRE	2014-06-23 +00:00	updated Relationships
CWE Content Team	MITRE	2014-07-30 +00:00	updated Relationships
CWE Content Team	MITRE	2015-12-07 +00:00	updated Relationships
CWE Content Team	MITRE	2017-11-08 +00:00	updated Applicable_Platforms, Demonstrative_Examples, Description, Enabling_Factors_for_Exploitation, Modes_of_Introduction, Observed_Examples, Relationships
CWE Content Team	MITRE	2018-03-27 +00:00	updated Relationships
CWE Content Team	MITRE	2019-06-20 +00:00	updated Relationships
CWE Content Team	MITRE	2021-10-28 +00:00	updated Relationships
CWE Content Team	MITRE	2022-10-13 +00:00	updated Relationships
CWE Content Team	MITRE	2023-01-31 +00:00	updated Description
CWE Content Team	MITRE	2023-04-27 +00:00	updated Relationships
CWE Content Team	MITRE	2023-06-29 +00:00	updated Mapping_Notes
CWE Content Team	MITRE	2025-12-11 +00:00	updated Relationships, Weakness_Ordinalities
CWE Content Team	MITRE	2026-04-30 +00:00	updated Observed_Examples
CWE Content Team	MITRE	2026-10-28 +00:00	updated Common_Consequences, Description, Technical_Nuance

Chi tiết CWE-640

CWE-640