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 1779844 - incorrectly labeled /usr/libexec/utempter/utempter
Summary: incorrectly labeled /usr/libexec/utempter/utempter
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: selinux-policy
Version: 7.8
Hardware: All
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Zdenek Pytela
QA Contact: Milos Malik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-04 20:48 UTC by Milos Malik
Modified: 2019-12-05 09:11 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1729571
Environment:
Last Closed: 2019-12-05 09:11:21 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Milos Malik 2019-12-04 20:48:13 UTC 
+++ This bug was initially created as a clone of Bug #1729571 +++

Description of problem:
 * SELinux policy defines types: utempter_t (process type) and utempter_exec_t (file type)
 * but there is an incorrect file context pattern which means that the utempter binary is not labeled utempter_exec_t which means that no process transitions into utempter_t domain

Version-Release number of selected component (if applicable):
libutempter-1.1.6-4.el7.x86_64
selinux-policy-3.13.1-266.el7.noarch
selinux-policy-devel-3.13.1-266.el7.noarch
selinux-policy-mls-3.13.1-266.el7.noarch
selinux-policy-targeted-3.13.1-266.el7.noarch

How reproducible:
 * always

Steps to Reproduce:
# semanage fcontext -l | grep utempter
/usr/sbin/utempter                      regular file       system_u:object_r:utempter_exec_t:s0 
# ls -l /usr/sbin/utempter
ls: cannot access '/usr/sbin/utempter': No such file or directory
# ls -lZ /usr/libexec/utempter/utempter
-rwx--s--x. root utmp system_u:object_r:utempter_exec_t:s0 /usr/libexec/utempter/utempter
# rpm -qf /usr/libexec/utempter/utempter
libutempter-1.1.6-4.el7.x86_64
#

Actual results:
 * /usr/libexec/utempter/utempter is labeled incorrectly

Expected results:
 * /usr/libexec/utempter/utempter is labeled correctly

Additional information:
 * the same problem is already fixed in RHEL-8.1
Comment 3 Lukas Vrabec 2019-12-05 09:11:21 UTC 
This issue was not selected to be included in Red Hat Enterprise Linux 7 because it is seen either as low or moderate impact to a small number of use-cases. The next minor release will be in Maintenance Support 1 Phase, which means that qualified Critical and Important Security errata advisories (RHSAs) and Urgent Priority Bug Fix errata advisories (RHBAs) may be released as they become available.

We will now close this issue, but if you believe that it qualifies for the Maintenance Support 1 Phase, please re-open; otherwise, we recommend moving the request to Red Hat Enterprise Linux 8 if applicable.
Note You need to log in before you can comment on or make changes to this bug.