• Authentication

Broken Authentication

Broken authentication covers flaws in how users prove who they are — weak login flows, session handling, credential recovery, and MFA gaps that let attackers take over accounts.

How attackers abuse it

Attackers spray breached passwords, brute-force poorly rate-limited logins, and abuse password-reset flows that leak whether an email exists or accept token fixation.

Session issues — predictable tokens, missing rotation on login, long-lived cookies without Secure/HttpOnly — let stolen tokens persist. “Remember me” without device binding widens the window.

MFA bypasses (fallback codes, race conditions, session upgrade without re-auth) turn a password leak into full account control.

What proof looks like

Proof shows a concrete authentication failure: session reuse after logout/password change, reset-token abuse, MFA skip, or credential stuffing success against a test account — documented with requests and outcomes, not a generic “weak password policy” opinion.

In PandaONE, this class maps to the Authentication finding category. Alerts ship only with evidence — never as unverified scanner noise.

How to prevent it

  • Enforce strong password storage (modern KDFs), rate limits, and lockout/backoff.
  • Rotate session identifiers on login and privilege change; invalidate on logout and reset.
  • Design reset and invite flows with single-use, short-lived, high-entropy tokens.
  • Require MFA for sensitive roles; treat backup codes as secrets.
  • Monitor anomalous auth events and alert on credential stuffing patterns.

• FAQ

Frequently asked questions

← All vulnerability classes

Hunt this class with proof

Or scan your domain.

Featured on ScrollLaunchFeatured on CodeHype