Unverified Password Change

Opis

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

This could be used by an attacker to change passwords for another user, thus gaining the privileges associated with that user.

Skutki

• Access Control

  Bypass Protection Mechanism; Gain Privileges or Assume Identity

Zapobieganie

• 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.

Przykłady podatności

• CVE-2025-4903 Router web interface allows unverified password change
• 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.

Słabość nadrzędna

• CWE-1390 Weak Authentication

Kiedy powstaje

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

Dotyczy

Not Language-Specific, Not Technology-Specific

Źródła

1. 24 Deadly Sins of Software Security — Michael Howard, David LeBlanc, John Viega, "Sin 19: Use of Weak Password-Based Systems." Page 279, McGraw-Hill, 2010