Replies: 1 comment
-
|
related to: #41331 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
The "forgot password" process does not currently restrict an attacker from automating what should only be a manual process. An attacker could automate sending thousands of password reset emails or user invitations. As a result, legitimate users might assume that the customer (owner of the Keycloak instance) is spamming them.
Attackers could also exploit this to defame or annoy users, ultimately harming the customerβs brand.
Is there an existing mechanism to prevent this?
As far as I understand, brute-force protection can only be enabled on the login page, correct?
(ext. ref: epic#1248)
Beta Was this translation helpful? Give feedback.
All reactions