Last Modified: Aug 25, 2025
Affected Product(s):
F5OS F5OS-A
Known Affected Versions:
F5OS-A 1.8.0
Opened: Aug 20, 2025 Severity: 3-Major
The "last-change" field gets updated date when a user changes their password and this can be verified with this command: # show system aaa authentication users user <name> When the password is updated at certain time during the day, the last-change field does not reflect the correct date and it could report a date that is a day older due to timezone misalignment.
There is no negative impact besides erroneous reporting of information within the "last-change" field. The user's password still gets updated.
A local user changes or resets their own password, resulting in the "last-change" field to get updated. When the “set-password” command is used by a user with Administrator privilege to change another user's password, it now sets the user’s “last-change” field to zero. This triggers a forced password change at the next login, ensuring that the user sets their own password rather than relying on one set by another account, even if that account is an administrator. If the user changes their own password, it will automatically update "last-change" field to the date when password got reset and it will be in the format 'YYYY-MM-DD'. This issue only occurs on rSeries appliances. This issue only occurs when the system timezone is configured to something other than UTC.
You can manually set the “last-change” field to the current date after the password change with the following commands: (1) Enter configuration prompt mode after logging in as a user with Administrator privilege: # config terminal (2) Manually set the last-change field to the current date at the time of the change and then commit the change: # system aaa authentication users user <username> config last-change YYYY-MM-DD; commit and-quit Replace YYYY-MM-DD with the relevant year, month and date.
None