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.

Bug 1856466

Summary: RHEL 8 (including UBI) fails no_empty_passwords check.
Product: Red Hat Enterprise Linux 8 Reporter: James Hartsock <hartsjc>
Component: scap-security-guideAssignee: Vojtech Polasek <vpolasek>
Status: CLOSED ERRATA QA Contact: Milan Lysonek <mlysonek>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.3CC: ekasprzy, ekolesni, ggasparb, matyc, mhaicman, mlysonek, vpolasek, wsato
Target Milestone: rcKeywords: AutoVerified, Reopened, Triaged
Target Release: ---Flags: lcervako: mirror+
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: scap-security-guide-0.1.57-1.el8 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-11-09 18:43:58 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description James Hartsock 2020-07-13 17:43:00 UTC
Description of problem:
RHEL 7 & RHEL 8 (including UBI) fail no_empty_passwords check. However, both platforms have had BZs/RFE closed as won't fix as do not see this as an issue.  Based on this it seems that oscap should be changed to not only check for 'nullok', but also if any user has emtpy password (which per pam BZs is not case for fresh RHEL/UBI).

  BZ 1640731 RHEL7:authconfig - disable nullok using a flag from authconfig
  BZ 1637936 RHEL8:authselect - Default to a "nonullok" profile to authselect


Version-Release number of selected component (if applicable):
pam-1.1.8-23.el7.x86_64
openscap-1.2.17-9.el7.x86_64


How reproducible:
100%

Steps to Reproduce:
1. Start RHEL 7 UBI
   # podman run --rm -it registry.access.redhat.com/ubi7/ubi:latest /bin/bash

2. Add repo that has oscap
   [rhel-7-server-rpms]
   baseurl = http://172.31.0.1/repos/rhel-7-server-rpms
   enabled=1
   gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release

3. Install opensacp
   # yum install openscap{,-scanner} scap-security-guide

4. Run oscap, will fail no_empty_passwords check
   # oscap xccdf eval --fetch-remote-resources --profile standard --rule no_empty_passwords \
     /usr/share/xml/scap/ssg/content/ssg-rhel7-xccdf.xml


Actual results:
  Title   Prevent Login to Accounts With Empty Password
  Rule    no_empty_passwords
  Ident   CCE-27286-4
  Result  fail


Expected results:
  Red Hat provided UBI should not fail any oscap standard profile checks


Additional info:

  RHEL 7 has even added comment about nullok in the Security Doc

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/security_guide/chap-hardening_your_system_with_tools_and_services#sect-Security_Guide-Workstation_Security-Account_Locking

Comment 8 Chris Williams 2020-11-11 21:55:12 UTC
Red Hat Enterprise Linux 7 shipped it's final minor release on September 29th, 2020. 7.9 was the last minor releases scheduled for RHEL 7.
From intial triage it does not appear the remaining Bugzillas meet the inclusion criteria for Maintenance Phase 2 and will now be closed. 

From the RHEL life cycle page:
https://access.redhat.com/support/policy/updates/errata#Maintenance_Support_2_Phase
"During Maintenance Support 2 Phase for Red Hat Enterprise Linux version 7,Red Hat defined Critical and Important impact Security Advisories (RHSAs) and selected (at Red Hat discretion) Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available."

If this BZ was closed in error and meets the above criteria please re-open it flag for 7.9.z, provide suitable business and technical justifications, and follow the process for Accelerated Fixes:
https://source.redhat.com/groups/public/pnt-cxno/pnt_customer_experience_and_operations_wiki/support_delivery_accelerated_fix_release_handbook  

Feature Requests can re-opened and moved to RHEL 8 if the desired functionality is not already present in the product. 

Please reach out to the applicable Product Experience Engineer[0] if you have any questions or concerns.  

[0] https://bugzilla.redhat.com/page.cgi?id=agile_component_mapping.html&product=Red+Hat+Enterprise+Linux+7

Comment 22 Vojtech Polasek 2021-07-02 09:56:16 UTC
Fixed upstream:
https://github.com/ComplianceAsCode/content/pull/7154

Comment 33 errata-xmlrpc 2021-11-09 18:43:58 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (scap-security-guide bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2021:4265