Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
IdM does not check Minimum life of password when performing password changing, if a very high minlife value is set.
==========
$ ipa pwpolicy-show --user=bob
Group: non_expired_passwd_group
Min lifetime (hours): 99999
Grace login limit: -1
[bob@node-0 ~]$ passwd
Changing password for user bob.
Current Password:
New password:
Retype new password:
Password change failed. Server message: Current password's minimum life has not expired
Password not changed.
passwd: Authentication token manipulation error
==========
Change lifetime to 10x larger to previous run:
==========
[bob@node-0 ~]$ ipa pwpolicy-show --user=bob
Group: non_expired_passwd_group
Min lifetime (hours): 999999
Grace login limit: -1
[bob@node-0 ~]$ passwd
Changing password for user bob.
Current Password:
New password:
Retype new password:
passwd: all authentication tokens updated successfully.
Version-Release number of selected component (if applicable):
How reproducible:
100%
Actual results:
Password changing is allowed even if age of password is within minlife.
Expected results:
1. IdM checks acceptable range of integer when adding/modifying a password policy, and rejects ridiculously high values, or
2. IdM enforces password policy for whatever minlife value saved in policy.
Additional info:
Sounds like an integer overflow. What is the use-case for using a huge case for minimum lifetime? Is it to disallow users from changing their own passwords?
> What is the use-case for using a huge case for minimum lifetime? Is it to disallow users from changing their own passwords?
Yes, initially I was testing if it would be a possible option.
Regardless what the use-case is, validation should be performed when either: (1) value is set in pwpolicy, or (2) user is changing password.
Reproduced. Doesn't look like an integer overflow. The time values are timestamps so not even half a 32-bit integer:
from util/ipa_pwd.c:
if (cur_time < last_pwd_change + policy->min_pwd_life) {
return IPAPWD_POLICY_PWD_TOO_YOUNG;
}
So something else is going on.
Comment 4RHEL Program Management
2023-09-18 22:54:14 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 5RHEL Program Management
2023-09-18 23:34:39 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.