Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tokens can be brute forced if 'Clear failcounter after minutes' is not zero #1578

Closed
droobah opened this issue Apr 16, 2019 · 1 comment

Comments

Projects
None yet
2 participants
@droobah
Copy link
Contributor

commented Apr 16, 2019

It appears that if 'Clear failcounter after minutes' is set to a non-zero value, after that timeout expires, any token can be brute forced.

I believe one of two options could be pursued to mitigate this.

Option #1 (more security, less user-friendly):
After the failcounter is exceeded, any additional failed attempt will 'reset' the fail exceeded counter and restart the timeout.

Option #2 (more user-friendly):
After the failcounter is exceeded, truly reset the failcounter to 0 so that the user would have more attempts before they are locked out again.

I believe #1 would be easier to implement programatically.

Community Thread:
https://community.privacyidea.org/t/failcount-automatic-clearing-and-brute-forcing/1005/3

@cornelinux

This comment has been minimized.

Copy link
Member

commented Apr 16, 2019

Thanks! Actually we already fixed this here
#1574
We developed a work-around using event handlers, which we will publish shortly.

@droobah here is the workaround: https://www.privacyidea.org/reset-failcounter-using-event-handlers/

@cornelinux cornelinux closed this Apr 16, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.