Broken authentication meaning, in plain words

Broken authentication means a login mechanism weak enough to be broken through. How it happens, why password reset matters, and defenses, per OWASP and MITRE.

Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated

Broken authentication means a login mechanism is weak enough to be broken through. It describes a hole in the stage that confirms who someone is. It covers not only the password entry field but also the entry points for reset and recovery.

How does broken authentication work?

Picture a company reception that lets someone in just because they gave a name. Even if reception does check identity, a loophole in the procedure produces the same result.

OWASP's API Security Top 10 2023 treats the entry points and flows of authentication as assets to protect, and asks that password reset and recovery be protected as strongly. Examples of a weak state include being able to try large numbers of leaked ID and password pairs, and guessing many times without being stopped. Accepting weak passwords, and being able to change an email address without checking the current password, are in the same list.

It also covers faults in handling the token (a pass showing the user is logged in): not checking expiry, insufficient signatures, and putting it in the URL. Specific points to check are explained on the API authentication flaws page.

Why does broken authentication matter?

Once login is broken through, screen operations and data retrieval go ahead as that person. Brute force, which guesses passwords, and credential stuffing, which uses leaked combinations, succeed more easily on sites with weak authentication. On a site with members or customers, the damage reaches users.

The measures OWASP gives start with listing the login and reset routes. Then use established standards and do not build your own scheme. When the email address or the phone number for two-step authentication is changed, ask for identity confirmation again.

Limits on attempts are advised to be stricter than for a general API. Where possible, add two-factor authentication, which asks for one more confirmation in addition to the password. Consider it together with rate limiting.

To check whether your login and reset flows are covered, contact us.

Related terms

  • Two-factor authentication: asking for one more confirmation in addition to the password.
  • Brute force: an attack that tries passwords one after another.
  • Credential stuffing: trying leaked IDs and passwords on another service.
  • Rate limiting: narrowing how many requests are accepted when many arrive in a short time.
  • Passkey: logging in with a fingerprint or face, without a password.

Next step

The overall picture of checking authentication in an API or login feature is on the API authentication flaws page. The free URL check shows only what is visible from outside. For checking your defenses including reset flows, contact us.

Frequently asked questions

How is broken authentication different from broken access control?

Authentication is the stage that confirms who you are, and access control is the stage that decides what that person may do. A problem where login is broken through belongs to the former, and one where information that should not be visible can be seen after login belongs to the latter.

Does a longer password prevent broken authentication?

No. A long password helps, but problems in the mechanism remain, such as no limit on attempts or a weak reset procedure. Consider adding multi-factor authentication too.

Frequently asked questions

How is broken authentication different from broken access control?

Authentication is the stage that confirms who you are, and access control is the stage that decides what that person may do. A problem where login is broken through belongs to the former, and one where information that should not be visible can be seen after login belongs to the latter.

Does a longer password prevent broken authentication?

No. A long password helps, but problems in the mechanism remain, such as no limit on attempts or a weak reset procedure. Consider adding multi-factor authentication too.

See what an attacker can see, today

The free URL check returns a grade in under a minute. For costs and next steps, book a free consultation.