zitadel/internal/auth/repository
Livio Spring a1d24353db
fix: prevent error reason leakage in case of IgnoreUnknownUsernames (#8372)
# Which Problems Are Solved

ZITADEL administrators can enable a setting called "Ignoring unknown
usernames" which helps mitigate attacks that try to guess/enumerate
usernames. If enabled, ZITADEL will show the password prompt even if the
user doesn't exist and report "Username or Password invalid".
Due to a implementation change to prevent deadlocks calling the
database, the flag would not be correctly respected in all cases and an
attacker would gain information if an account exist within ZITADEL,
since the error message shows "object not found" instead of the generic
error message.

# How the Problems Are Solved

- Proper check of the error using an error function / type and
`errors.Is`

# Additional Changes

None.

# Additional Context

- raised in a support request

Co-authored-by: Silvan <silvan.reusser@gmail.com>
2024-07-31 14:23:57 +02:00
..
eventsourcing fix: prevent error reason leakage in case of IgnoreUnknownUsernames (#8372) 2024-07-31 14:23:57 +02:00
auth_request.go feat(idp): provide option to auto link user (#7734) 2024-04-10 15:46:30 +00:00
org.go feat(login): use new IDP templates (#5315) 2023-02-28 21:20:58 +01:00
refresh_token.go chore: upgrade to oidc v2 release (#5437) 2023-03-28 11:28:56 +00:00
repository.go fix: move activity log to queries and remove old code (#3096) 2022-01-26 10:16:33 +01:00
token.go feat(eventstore): increase parallel write capabilities (#5940) 2023-10-19 12:19:10 +02:00
user_session.go refactor: cleanup unused code (#7130) 2024-01-02 14:26:31 +00:00
user.go fix: change to repository event types and removed unused code (#3386) 2022-03-31 11:36:26 +02:00