Password reset binding or single-use failure
Recovery proof can change the wrong account or be reused contrary to the recovery contract.
Candidate CWE: CWE-640
Test hypothesis#
Request recovery for two controlled inboxes. In the replica, change only the client-controlled account selector when submitting A’s proof. Separately replay a consumed proof once after a successful reset.
Evidence required#
A fresh login verifies the wrong controlled account changed, or a consumed proof changes a credential again. Record issuance, intended subject, consumption time, and result without publishing the proof.
Rule out false positives#
A reset form remaining visible, a generic success page, and repeated submission that makes no credential change are not sufficient.
Playbook and command references#
- Authentication, recovery, federation, and session lifecycle — Test registration, recovery, identity changes, invitations, SSO enforcement, and deprovisioning as one account state machine.
Find the associated command snippets
Referenced by these target playbooks#
Report checklist#
- Capture the affected version, configuration, identities, and object ownership.
- Preserve a valid baseline and a negative control.
- Reproduce the forbidden data access, action, or state change on controlled fixtures.
- Explain the intended security rule and why the observed behavior violates it.
- State prerequisites, uncertainty, cleanup, and the smallest demonstrated impact.
Conditional ATT&CK mapping#
No direct ATT&CK mapping selected. Record the weakness and demonstrated impact without forcing an adversary-behavior classification. See the mapping guide.