CWE-620 詳細資料

When setting a new password for a user, the product does not require knowledge of the original password, or using another form of authentication.

引入方式

Architecture and Design
Implementation : REALIZATION: This weakness is caused during implementation of an architectural security tactic.

適用平台

程式語言

類別： Not Language-Specific (Undetermined)

技術

類別： Not Technology-Specific (Undetermined)

常見後果

觀察到的案例

潛在緩解措施

Phases : Architecture and Design
When prompting for a password change, force the user to provide the original password in addition to the new password.
Phases : Architecture and Design
Do not use "forgotten password" functionality. But if you must, ensure that you are only providing information to the actual user, e.g. by using an email address or challenge question that the legitimate user already provided in the past; do not allow the current user to change this identity information until the correct password has been provided.

漏洞對應備注

理由說明 : This CWE entry is at the Base level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.
備註 : Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.

參考資料

REF-44

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

提交

修改記錄