Bug 2228467 - Rules "Set Existing Passwords Maximum/Minimum Age" apply to non-local users as well [rhel-9.2.0.z]
Summary: Rules "Set Existing Passwords Maximum/Minimum Age" apply to non-local users a...
Keywords:
Status: ON_QA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: scap-security-guide
Version: 9.2
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Jan Černý
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On: 2213958
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-08-02 12:23 UTC by RHEL Program Management Team
Modified: 2023-08-17 00:49 UTC (History)
9 users (show)

Fixed In Version: scap-security-guide-0.1.69-1.el9_2
Doc Type: Bug Fix
Doc Text:
.Password age rules apply only to local users Some compliance profiles, eg. CIS or DISA STIG, contain rules checking password age and password expiration of user account passwords. Specifically, we are talking about these rules: accounts_password_set_max_life_existing, accounts_password_set_min_life_existing, accounts_password_set_warn_age_existing, accounts_set_post_pw_existing. Previously, these rules checked not only configuration of local users but they also evaluated configuration of remote users provided by network sources such as NSS. This behavior was caused by using the `getpwent()` system call in the OpenSCAP scanner. This behavior wasn't desired, behavior the remediation scripts weren't able to change the configuration of the remote users. Therefore, the internal implementation of the aforementioned rules has been changed to depend only on data present in the "/etc/shadow" file. That means no other sources of user metadata are read by the rules. As a result, the rules now consider only local users configuration.
Clone Of: 2213958
Environment:
Last Closed:
Type: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-164213 0 None None None 2023-08-02 14:27:00 UTC


Note You need to log in before you can comment on or make changes to this bug.