CWE-620: Unverified Password Change
When setting a new password for a user, the product does not require knowledge of the original password, or using another form of authentication.
How it's found
Unverified Password Change is typically found by tracing untrusted input from where it enters the system to the point where it is used without the check or neutralization this weakness describes, combining manual code review with dynamic testing.
This could be used by an attacker to change passwords for another user, thus gaining the privileges associated with that user.
Consequences
- Bypass Protection Mechanism, Gain Privileges or Assume Identity
Mitigations
- 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.
Where this fits in a TurboPentest engagement
This weakness is not covered by the automated black-box pentest. IntegSec pentesters cover it in a manual engagement.
Frequently asked questions
What is 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.
How do you find Unverified Password Change?
Unverified Password Change is typically found by tracing untrusted input from where it enters the system to the point where it is used without the check or neutralization this weakness describes, combining manual code review with dynamic testing.
What is the impact of CWE-620?
Bypass Protection Mechanism, Gain Privileges or Assume Identity
Does TurboPentest test for Unverified Password Change?
This weakness is not covered by the automated black-box pentest. IntegSec pentesters cover it in a manual engagement.
Related CWEs
- Class weaknessCWE-1390: Weak Authentication
- Variant weaknessCWE-259: Use of Hard-coded Password
- Class weaknessCWE-287: Improper Authentication
- Base weaknessCWE-309: Use of Password System for Primary Authentication
- Class weaknessCWE-345: Insufficient Verification of Data Authenticity
- Compound weaknessCWE-384: Session Fixation
Written and reviewed by
Michel Chamberland - Founder & CEO, IntegSec
CISSP, OSCP, OSCE, CEH, GIAC, CCSK · 20+ years in offensive security
Michel has spent 20+ years on offensive security teams including IBM X-Force Red and Trustwave SpiderLabs, leading penetration tests, red team engagements, and breach response for Fortune 500 customers. He is the founder of IntegSec and the architect of TurboPentest.
Find these issues before an attacker does
TurboPentest runs an agentic AI pentest against your target and reports findings with proof, from $99 per target.
Start a pentest