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.
DescriptionJan Pazdziora (Red Hat)
2022-06-02 09:30:06 UTC
Description of problem:
The require_singleuser_auth SCAP rule says in its Description:
Single-user mode is intended as a system recovery method,
providing a single user root access to the system by providing a boot
option at startup. By default, no authentication is performed
if single-user mode is selected.
By default, single-user mode is protected by requiring a password and is set
in /usr/lib/systemd/system/rescue.service.
That is confusing -- is no authentication performed, or is password required?
Version-Release number of selected component (if applicable):
scap-security-guide-0.1.60-6.el9_0.noarch
How reproducible:
Deterministic.
Steps to Reproduce:
1. oscap xccdf eval --profile xccdf_org.ssgproject.content_profile_ospp --rule xccdf_org.ssgproject.content_rule_require_singleuser_auth --results results.html /usr/share/xml/scap/ssg/content/ssg-rhel9-ds.xml
2. Read the results.html.
Actual results:
Confusing information about authentication.
Expected results:
Default (unhardened) behaviour and the desired hardened behaviour clearly distinguished.
But note that at least on RHEL 9, the service is configured the way the rule wants it to (ExecStart=-/usr/lib/systemd/systemd-sulogin-shell rescue), so maybe the first "By default" should be dropped completely or be made conditional on the OS (and version)?
Additional info:
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-2022:8131
Description of problem: The require_singleuser_auth SCAP rule says in its Description: Single-user mode is intended as a system recovery method, providing a single user root access to the system by providing a boot option at startup. By default, no authentication is performed if single-user mode is selected. By default, single-user mode is protected by requiring a password and is set in /usr/lib/systemd/system/rescue.service. That is confusing -- is no authentication performed, or is password required? Version-Release number of selected component (if applicable): scap-security-guide-0.1.60-6.el9_0.noarch How reproducible: Deterministic. Steps to Reproduce: 1. oscap xccdf eval --profile xccdf_org.ssgproject.content_profile_ospp --rule xccdf_org.ssgproject.content_rule_require_singleuser_auth --results results.html /usr/share/xml/scap/ssg/content/ssg-rhel9-ds.xml 2. Read the results.html. Actual results: Confusing information about authentication. Expected results: Default (unhardened) behaviour and the desired hardened behaviour clearly distinguished. But note that at least on RHEL 9, the service is configured the way the rule wants it to (ExecStart=-/usr/lib/systemd/systemd-sulogin-shell rescue), so maybe the first "By default" should be dropped completely or be made conditional on the OS (and version)? Additional info: