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 1039879 - nm-dispatcher.action runs as initrc_t
Summary: nm-dispatcher.action runs as initrc_t
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: selinux-policy
Version: 7.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Miroslav Grepl
QA Contact: Milos Malik
URL:
Whiteboard:
Depends On: nopolicy
Blocks: 848829
TreeView+ depends on / blocked
 
Reported: 2013-12-10 08:56 UTC by Milos Malik
Modified: 2014-12-08 09:51 UTC (History)
0 users

Fixed In Version: selinux-policy-3.12.1-109.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-13 12:17:53 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Milos Malik 2013-12-10 08:56:31 UTC 
Description of problem:
 * nm-dispatcher.action uses too powerful SELinux domain

Version-Release number of selected component (if applicable):
NetworkManager-0.9.9.0-27.git20131108.el7.x86_64
NetworkManager-glib-0.9.9.0-27.git20131108.el7.x86_64
NetworkManager-openswan-0.9.8.0-1.el7.x86_64
selinux-policy-3.12.1-108.el7.noarch
selinux-policy-devel-3.12.1-108.el7.noarch
selinux-policy-doc-3.12.1-108.el7.noarch
selinux-policy-minimum-3.12.1-108.el7.noarch
selinux-policy-mls-3.12.1-108.el7.noarch
selinux-policy-targeted-3.12.1-108.el7.noarch

How reproducible:
always

Steps to Reproduce:
# service NetworkManager-dispatcher status
Redirecting to /bin/systemctl status  NetworkManager-dispatcher.service
NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service
   Loaded: loaded (/usr/lib/systemd/system/NetworkManager-dispatcher.service; enabled)
   Active: inactive (dead)

Dec 10 09:45:14 rhel70.localdomain systemd[1]: Starting Network Manager Scri....
Dec 10 09:45:14 rhel70.localdomain systemd[1]: Started Network Manager Scrip....
Dec 10 09:45:14 rhel70.localdomain logger[1199]: dnssec-trigger-hook(network...g
Dec 10 09:45:14 rhel70.localdomain logger[1201]: dnssec-trigger-hook(network...g
Dec 10 09:47:52 rhel70.localdomain systemd[1]: Starting Network Manager Scri....
Dec 10 09:47:52 rhel70.localdomain systemd[1]: Started Network Manager Scrip....
Dec 10 09:49:00 rhel70.localdomain systemd[1]: Starting Network Manager Scri....
Dec 10 09:49:00 rhel70.localdomain systemd[1]: Started Network Manager Scrip....
Dec 10 09:49:11 rhel70.localdomain systemd[1]: Stopped Network Manager Scrip....
Hint: Some lines were ellipsized, use -l to show in full.
# service NetworkManager-dispatcher start
Redirecting to /bin/systemctl start  NetworkManager-dispatcher.service
# service NetworkManager-dispatcher status
Redirecting to /bin/systemctl status  NetworkManager-dispatcher.service
NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service
   Loaded: loaded (/usr/lib/systemd/system/NetworkManager-dispatcher.service; enabled)
   Active: active (running) since Tue 2013-12-10 09:53:09 CET; 993ms ago
 Main PID: 2662 (nm-dispatcher.a)
   CGroup: /system.slice/NetworkManager-dispatcher.service
           └─2662 /usr/libexec/nm-dispatcher.action

Dec 10 09:53:09 rhel70.localdomain systemd[1]: Started Network Manager Scrip....
Hint: Some lines were ellipsized, use -l to show in full.
# ps -efZ | grep -e initrc_t -e init_t
system_u:system_r:init_t:s0     root         1     0  0 09:44 ?        00:00:01 /usr/lib/systemd/systemd --switched-root --system --deserialize 23
system_u:system_r:initrc_t:s0   root      2662     1  0 09:53 ?        00:00:00 /usr/libexec/nm-dispatcher.action
unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 root 2675 2575  0 09:53 pts/0 00:00:00 grep --color=auto -e initrc_t -e init_t
#

Actual results:
 * nm-dispatcher.action runs as initrc_t

Expected results:
 * nm-dispatcher.action runs as NetworkManager_t
Comment 1 Miroslav Grepl 2013-12-10 12:01:54 UTC 
Good catch. This is because of

ExecStart=/usr/libexec/nm-dispatcher.action
Comment 2 Miroslav Grepl 2013-12-10 12:04:07 UTC 
commit 06750edfe38b27ba61cd099a8c5fd16c52456cb0
Author: Miroslav Grepl <mgrepl>
Date:   Tue Dec 10 13:02:45 2013 +0100

    Change labeling for /usr/libexec/nm-dispatcher.action to NetworkManager_exec_t
Comment 5 Ludek Smid 2014-06-13 12:17:53 UTC 
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.
Note You need to log in before you can comment on or make changes to this bug.