You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
<
8000
div
class="application-main "
data-commit-hovercards-enabled
data-discussion-hovercards-enabled
data-issue-and-pr-hovercards-enabled
data-project-hovercards-enabled
>
Repository navigation
Feature to control the retry limit for 'forgot password' links.
#42162
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?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
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)
All reactions