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 10:39:18 UTC
Description of problem:
In the OSPP profile, there is a rule service_debug-shell_disabled.
However, per https://freedesktop.org/wiki/Software/systemd/Debugging/#earlydebugshell, the service can also be enabled by passing systemd.debug-shell=1 kernel command-line parameter. We'd need additional checks to guard against this parameter, likely in a new SCAP rule.
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. grubby --update-kernel=ALL --args=systemd.debug-shell=1
2. Reboot the system.
3. Check that there is a open root shell on ninth console.
4. oscap xccdf eval --profile xccdf_org.ssgproject.content_profile_ospp /usr/share/xml/scap/ssg/content/ssg-rhel9-ds.xml
Actual results:
No failure which would point it out.
Expected results:
Some SCAP rule about debug-shell which would fail in such situation.
Additional info:
The difference between this request and bug 2092809 where we ask for removal of similar check for systemd.confirm_spawn is, it is impossible to boot a system with systemd.confirm_spawn without noticing it, without the admin knowing they did not start TOE. On the other hand, with systemd.debug-shell=1 the system starts and operates just fine, there is just a gaping hole in the system allowing unauthenticated operations, which is a violation of FIA_UAU.1.
Comment 1Jan Pazdziora (Red Hat)
2022-06-02 10:48:02 UTC
I should note, we likely need both grub_ and zipl_ variants of this check.
Comment 4Watson Yuuma Sato
2022-07-11 11:55:38 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-2022:8131