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 1451358 - scap reports device files with device_t context as violating a rule
Summary: scap reports device files with device_t context as violating a rule
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: selinux-policy
Version: 7.3
Hardware: Unspecified
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Lukas Vrabec
QA Contact: Milos Malik
URL:
Whiteboard:
Depends On:
Blocks: 1420851
TreeView+ depends on / blocked
 
Reported: 2017-05-16 13:35 UTC by Zdenek Pytela
Modified: 2021-06-10 12:19 UTC (History)
7 users (show)

Fixed In Version: selinux-policy-3.13.1-174.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-10 12:29:42 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1451363 0 medium CLOSED scap tests report issues with symlinks whereas documentation mentions only plain files 2021-03-11 15:13:16 UTC
Red Hat Knowledge Base (Solution) 3062591 0 None None None 2017-05-31 14:58:23 UTC
Red Hat Product Errata RHBA-2018:0763 0 None None None 2018-04-10 12:32:07 UTC

Internal Links: 1451363

Description Zdenek Pytela 2017-05-16 13:35:13 UTC
Description of problem:
scap tests report device files with device_t SELinux context as violating the following rule:
Ensure No Device Files are Unlabeled by SELinux

Version-Release number of selected component (if applicable):
selinux-policy-3.13.1-102.el7_3.16.noarch

How reproducible:


Steps to Reproduce:
1. Run scap on latest RHEL 7

Actual results:
These files are reported with device_t context:
/dev/vsock
/dev/vmci
/dev/char/10:57
/dev/char/10:58

Expected results:
No files reported.

Additional info:
  # matchpathcon /dev/vmci /dev/vsock /dev/char/10:5[78]
/dev/vmci       system_u:object_r:device_t:s0
/dev/vsock      system_u:object_r:device_t:s0
/dev/char/10:57 system_u:object_r:device_t:s0
/dev/char/10:58 system_u:object_r:device_t:s0

These files: /dev/char/10:5[78]
are symlinks which are not displayed by the helper find command in 
http://static.open-scap.org/ssg-guides/ssg-rhel7-guide-stig-rhel7-server-upstream.html#xccdf_org.ssgproject.content_rule_selinux_all_devicefiles_labeled

The wording changed in a different document revision: Ensure No Device Files are Unknown to SELinux

Comment 4 Milos Malik 2017-10-24 13:55:51 UTC
Scap tests should skip symbolic links in /dev/char directory, because they are always labeled device_t.

Comment 8 errata-xmlrpc 2018-04-10 12:29:42 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, 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-2018:0763


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