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 1206525 - pmie and pmlogger do not run in dedicated domains
Summary: pmie and pmlogger do not run in dedicated domains
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: selinux-policy
Version: 7.3
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Lukas Vrabec
QA Contact: Jan Zarsky
URL:
Whiteboard:
: 1377804 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-27 11:01 UTC by Milos Malik
Modified: 2016-11-04 02:18 UTC (History)
10 users (show)

Fixed In Version: selinux-policy-3.13.1-98.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-04 02:18:07 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
AVCs when starting pmlogger in permissive mode (14.98 KB, text/plain)
2016-09-07 08:19 UTC, Jan Zarsky
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2283 0 normal SHIPPED_LIVE selinux-policy bug fix and enhancement update 2016-11-03 13:36:25 UTC

Description Milos Malik 2015-03-27 11:01:28 UTC
Description of problem:
 * one of our automated TCs found that pmie and pmlogger run as unconfined_service_t, which is not correct
 * other PCP services run in dedicated domains

Version-Release number of selected component (if applicable):
pcp-3.9.10-8.el7.x86_64
pcp-conf-3.9.10-8.el7.x86_64
pcp-libs-3.9.10-8.el7.x86_64
pcp-manager-3.9.10-8.el7.x86_64
pcp-webapi-3.9.10-8.el7.x86_64
selinux-policy-3.13.1-23.el7.noarch
selinux-policy-devel-3.13.1-23.el7.noarch
selinux-policy-doc-3.13.1-23.el7.noarch
selinux-policy-minimum-3.13.1-23.el7.noarch
selinux-policy-mls-3.13.1-23.el7.noarch
selinux-policy-sandbox-3.13.1-23.el7.noarch
selinux-policy-targeted-3.13.1-23.el7.noarch

How reproducible:
always

Steps to Reproduce:
# chkconfig pmie on
# chkconfig pmlogger on
# service pmcd start
# service pmie start
# service pmlogger start
# ps -efZ | grep pm

Actual results:
system_u:system_r:unconfined_service_t:s0 pcp 27556 1  0 11:53 ?       00:00:00 pmie -b -h local: -l /var/log/pcp/pmie/rhel71.localdomain/pmie.log -c config.default
system_u:system_r:unconfined_service_t:s0 pcp 28564 1  0 11:57 ?       00:00:00 pmlogger -P -r -T24h10m -c config.default -m pmlogger_check 20150327.11.57

Expected results:
 * pmie should run as pcp_pmie_t
 * pmlogger should run as pcp_pmlogger_t

Comment 13 Mike McCune 2016-03-28 22:58:03 UTC
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

Comment 15 Jan Zarsky 2016-09-06 12:04:06 UTC
As automated TC (/CoreOS/selinux-policy/Regression/pcp-daemons-and-similar) found out, pmlogger and pmie still runs as unconfined_service_t when started by systemd.

Version-Release number of selected component (if applicable):
pcp-3.11.3-4.el7.ppc64
selinux-policy-3.13.1-96.el7.noarch

Actual results:
# grep "ExecStart" /usr/lib/systemd/system/pmie.service
ExecStart=/usr/share/pcp/lib/pmie start

# matchpathcon /usr/share/pcp/lib/pmie
/usr/share/pcp/lib/pmie	system_u:object_r:lib_t:s0

# grep "ExecStart" /usr/lib/systemd/system/pmlogger.service
ExecStart=/usr/share/pcp/lib/pmlogger start

# matchpathcon /usr/share/pcp/lib/pmlogger
/usr/share/pcp/lib/pmlogger	system_u:object_r:lib_t:s0

Expected results:
# matchpathcon /usr/share/pcp/lib/pmlogger
/usr/share/pcp/lib/pmlogger	system_u:object_r:pcp_pmlogger_exec_t:s0
# matchpathcon /usr/share/pcp/lib/pmie
/usr/share/pcp/lib/pmie	system_u:object_r:pcp_pmie_exec_t:s0

Comment 18 Jan Zarsky 2016-09-07 08:18:05 UTC
Could not start pmlogger service, getting AVCs. Service pmie starts fine.

Version-Release number of selected component (if applicable):
selinux-policy-3.13.1-97.el7.noarch
pcp-3.11.3-4.el7.x86_64

Actual results:
# systemctl start pmcd
# systemctl start pmlogger
Job for pmlogger.service failed because the control process exited with error code. See "systemctl status pmlogger.service" and "journalctl -xe" for details.

Running in enforcing mode:
# systemctl status pmlogger
● pmlogger.service - Performance Metrics Archive Logger
   Loaded: loaded (/usr/lib/systemd/system/pmlogger.service; disabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Wed 2016-09-07 04:15:19 EDT; 8s ago
     Docs: man:pmlogger(1)
  Process: 25967 ExecStop=/usr/share/pcp/lib/pmlogger stop (code=exited, status=1/FAILURE)
  Process: 25975 ExecStart=/usr/share/pcp/lib/pmlogger start (code=exited, status=1/FAILURE)
 Main PID: 25975 (code=exited, status=1/FAILURE)

Sep 07 04:15:19 qeos-124.lab.eng.rdu2.redhat.com systemd[1]: Unit pmlogger.service entered failed state.
Sep 07 04:15:19 qeos-124.lab.eng.rdu2.redhat.com systemd[1]: pmlogger.service failed.
Sep 07 04:15:19 qeos-124.lab.eng.rdu2.redhat.com systemd[1]: Starting Performance Metrics Archive Logger...
Sep 07 04:15:19 qeos-124.lab.eng.rdu2.redhat.com pmlogger[25975]: /etc/pcp.env: line 46: /usr/bin/sed: Permission denied
Sep 07 04:15:19 qeos-124.lab.eng.rdu2.redhat.com pmlogger[25975]: /etc/pcp.env: line 46: /usr/bin/awk: Permission denied
Sep 07 04:15:19 qeos-124.lab.eng.rdu2.redhat.com pmlogger[25975]: /usr/share/pcp/lib/pmlogger: line 37: /lib/rc-proc.sh: No such file or directory
Sep 07 04:15:19 qeos-124.lab.eng.rdu2.redhat.com systemd[1]: pmlogger.service: main process exited, code=exited, status=1/FAILURE
Sep 07 04:15:19 qeos-124.lab.eng.rdu2.redhat.com systemd[1]: Failed to start Performance Metrics Archive Logger.
Sep 07 04:15:19 qeos-124.lab.eng.rdu2.redhat.com systemd[1]: Unit pmlogger.service entered failed state.
Sep 07 04:15:19 qeos-124.lab.eng.rdu2.redhat.com systemd[1]: pmlogger.service failed.

# ausearch -m avc
----
time->Wed Sep  7 04:01:38 2016
type=SYSCALL msg=audit(1473235298.845:356): arch=c000003e syscall=2 success=no exit=-13 a0=7fdbba82aa5d a1=80000 a2=1b6 a3=24 items=0 ppid=1 pid=8924 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="pmlogger" exe="/usr/bin/bash" subj=system_u:system_r:pcp_pmlogger_t:s0 key=(null)
type=AVC msg=audit(1473235298.845:356): avc:  denied  { read } for  pid=8924 comm="pmlogger" name="meminfo" dev="proc" ino=4026532028 scontext=system_u:system_r:pcp_pmlogger_t:s0 tcontext=system_u:object_r:proc_t:s0 tclass=file
----
time->Wed Sep  7 04:01:38 2016
type=SYSCALL msg=audit(1473235298.847:357): arch=c000003e syscall=21 success=no exit=-13 a0=11e74c0 a1=1 a2=7ffc7f36b670 a3=7ffc7f36b4c0 items=0 ppid=8925 pid=8926 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="pmlogger" exe="/usr/bin/bash" subj=system_u:system_r:pcp_pmlogger_t:s0 key=(null)
type=AVC msg=audit(1473235298.847:357): avc:  denied  { execute } for  pid=8926 comm="pmlogger" name="sed" dev="dm-1" ino=3681 scontext=system_u:system_r:pcp_pmlogger_t:s0 tcontext=system_u:object_r:bin_t:s0 tclass=file

... (lots of similar 'denied { execute }' for tcontext bin_t)

# ausearch -m avc | audit2allow
#============= pcp_pmlogger_t ==============

#!!!! WARNING: 'bin_t' is a base type.
allow pcp_pmlogger_t bin_t:file execute;
allow pcp_pmlogger_t proc_t:file read;


Running in permissive mode:
# ausearch -m avc
(too long - see attachment)

# ausearch -m avc | audit2allow
#============= pcp_pmlogger_t ==============

#!!!! WARNING: 'bin_t' is a base type.
allow pcp_pmlogger_t bin_t:file { execute execute_no_trans };
allow pcp_pmlogger_t hostname_exec_t:file { execute execute_no_trans getattr open read };

#!!!! The file '/run/systemd/private' is mislabeled on your system.  
#!!!! Fix with $ restorecon -R -v /run/systemd/private
allow pcp_pmlogger_t init_t:unix_stream_socket connectto;
allow pcp_pmlogger_t initrc_var_run_t:file { lock open read };
allow pcp_pmlogger_t proc_t:dir read;
allow pcp_pmlogger_t proc_t:file { getattr open read };
allow pcp_pmlogger_t self:capability { chown net_admin };

#!!!! WARNING: 'shell_exec_t' is a base type.
allow pcp_pmlogger_t shell_exec_t:file { execute execute_no_trans };
allow pcp_pmlogger_t systemd_systemctl_exec_t:file { execute execute_no_trans getattr open read };
allow pcp_pmlogger_t systemd_unit_file_t:file getattr;

Comment 19 Jan Zarsky 2016-09-07 08:19:14 UTC
Created attachment 1198579 [details]
AVCs when starting pmlogger in permissive mode

Comment 26 Nathan Scott 2016-09-21 12:41:43 UTC
*** Bug 1377804 has been marked as a duplicate of this bug. ***

Comment 28 errata-xmlrpc 2016-11-04 02:18:07 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://rhn.redhat.com/errata/RHBA-2016-2283.html


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