Unverified Password Change
|ID: 620||Date: (C)2012-05-14 (M)2012-11-08|
|Type: weakness||Status: DRAFT|
|Abstraction Type: Variant|
When setting a new password for a user, the product does not
require knowledge of the original password, or using another form of
Extended DescriptionThis could be used by an attacker to change passwords for another user,
thus gaining the privileges associated with that user.
Applicable PlatformsLanguage Class: All
Time Of Introduction
- Architecture and Design
|Access_Control ||Bypass protection
mechanismGain privileges / assume
identity || |
|Architecture and Design || ||When prompting for a password change, force the user to provide the
original password in addition to the new password. || || |
|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. || || |
|CWE-620 ChildOf CWE-898 ||Category ||CWE-888 || |
Demonstrative Examples (Details)
- This code changes a user's password. (Demonstrative Example Id DX-56)
- CVE-2007-0681 : Web app allows remote attackers to change the passwords of arbitrary users without providing the original password, and possibly perform other unauthorized actions.
- CVE-2000-0944 : Web application password change utility doesn't check the original password.
For more examples, refer to CVE relations in the bottom box.
White Box Definitions None
Black Box Definitions None
|OWASP Top Ten 2004 ||A3 ||Broken Authentication and Session
Management ||CWE_More_Specific |
- Michael Howard David LeBlanc John Viega .24 Deadly Sins of Software Security. McGraw-Hill. Section:'"Sin 19: Use of Weak Password-Based Systems." Page
279'. Published on 2010.