Cybersecurity
Hunt Forgot Password
Hunt Forgot Password / Account Recovery Authentication Flaws — 5 distinct patterns: (1) username enumeration via different responses for valid vs invalid email, (2) reset token exposed directly in the API response body, (3) reset token not invalidated after use (replay), (4) password reset link works from a different IP/browser (no binding), (5) no rate limit on the reset request endpoint. These are the standalone recovery-flow broken-auth primitives — distinct from reset-email host-header poisoning (hunt-host-header) and the full ATO chain (hunt-ato owns password-reset as an ATO path; prove the primitive here, chain it there). Detection: trace the full forgot-password flow from request to token to use; check response diffs between valid/invalid emails; test token replay after consumption. Medium to High (enumeration=Medium, token-reuse=High, account-takeover=Critical when chained to known-email).
- Publisher / source
- elementalsouls/Claude-BugHunter (found on GitHub top repositories)
- Upstream record
- elementalsouls/Claude-BugHunter
- Version
- Version 1
- Published
- Publication review
- Approved for publication · recorded passed scan 2026-11-05
- Content fingerprint
b484286559f091f3dc8cab21a43e47f4d7fbe00382f5bade799fb40c7101fb1e