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 1941666 - Relax rule on "SELINUXTYPE=XXX" setting
Summary: Relax rule on "SELINUXTYPE=XXX" setting
Keywords:
Status: CLOSED DUPLICATE of bug 1914226
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: scap-security-guide
Version: 7.9
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Vojtech Polasek
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-03-22 15:03 UTC by Renaud Métrich
Modified: 2024-06-14 00:57 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-03-23 11:12:04 UTC
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)

Description Renaud Métrich 2021-03-22 15:03:18 UTC 
Description of problem:

This is a continuation of BZ #1941661.
The rule "xccdf_org.ssgproject.content_rule_selinux_policytype" in scap-security-guide is too strict and also not correct on RHEL7:

linux_os/guide/system/selinux/selinux_policytype/oval/shared.xml:
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
 28   <ind:textfilecontent54_object id="obj_selinux_policy" version="1">
 29     <ind:filepath>/etc/selinux/config</ind:filepath>
 30     <ind:pattern operation="pattern match">^[\s]*SELINUXTYPE[\s]*=[\s]*([^\s]*)</ind:pattern>
 31     <ind:instance datatype="int">1</ind:instance>
 32   </ind:textfilecontent54_object>
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------

This states that you can have spaces before and after "=" sign, which is not true because SELINUXTYPE is a shell script variable.

Additionally it expects no trailing space after the value, e.g. "SELINUXTYPE=targeted<space>" will fail, which is the case because /etc/selinux/config ships the file with a trailing space (see BZ #1941661).

Please fix the rule as it was done in Upstream:

linux_os/guide/system/selinux/selinux_policytype/oval/shared.xml:
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
 24   <ind:textfilecontent54_object id="obj_selinux_policy" version="1">
 25     <ind:filepath>/etc/selinux/config</ind:filepath>
 26     <ind:pattern operation="pattern match">^SELINUXTYPE=([\w]*)[\s]*$</ind:pattern>
 27     <ind:instance datatype="int">1</ind:instance>
 28   </ind:textfilecontent54_object>
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------


Version-Release number of selected component (if applicable):

scap-security-guide-0.1.52-2.el7_9.noarch


How reproducible:

Always

Steps to Reproduce:
1. On a basic RHEL7 system, execute the rule

  # oscap xccdf eval --rule xccdf_org.ssgproject.content_rule_selinux_policytype --profile xccdf_org.ssgproject.content_profile_stig /usr/share/xml/scap/ssg/content/ssg-rhel7-ds.xml

Actual results:

Result  fail

Expected results:

No failure, even with default /etc/selinux/config content

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