Last Modified: Jul 15, 2026
Affected Product(s):
F5OS Velos
Known Affected Versions:
F5OS-A 1.5.2, F5OS-A 1.5.3, F5OS-A 1.5.4, F5OS-A 1.8.0, F5OS-A 1.8.1, F5OS-A 1.8.2, F5OS-A 1.8.3, F5OS-A 1.8.4, F5OS-C 1.6.0, F5OS-C 1.6.1, F5OS-C 1.6.2, F5OS-C 1.6.4, F5OS-C 1.8.0, F5OS-C 1.8.1, F5OS-C 1.8.2
Fixed In:
F5OS v2.0.0, F5OS v2.0.0
Opened: Dec 18, 2024 Severity: 3-Major
The administrator can set up the max-login-failures (Number of unsuccessful login attempts allowed before lockout) to a non-zero number. Also, the unlock-timeout can be increased from the default value of 60 seconds. Once the number of failed login attempts is reached, then the user must wait the alotted unlock-timeout period before being allowed to login with the correct credentials. The number of login-failures for each user is currently reset to zero upon a system reboot.
The max-login-failures setting is set back to zero if the system is rebooted.
Rebooting simply eliminates the tally count of login failures for all users.
None
With this fix, rebooting does not reset the tally count for login failures. This can be verified by viewing the state of the user: show system aaa authentication users user <user> state which will not go to zero after a reboot.