Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
We have a customer executing some sssd client command in a system cronjob (hence running as *system_cronjob_t*). We can see sssd cannot answer to the query due to a USER_AVC:
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
type=USER_AVC ... subj=system_u:system_r:system_dbusd_t:s0-s0:c0.c1023 msg='avc: denied { send_msg } for msgtype=method_return dest=:1.103521 ... scontext=system_u:system_r:sssd_t:s0 tcontext=system_u:system_r:system_cronjob_t:s0-s0:c0.c1023 tclass=dbus permissive=0 exe="/usr/bin/dbus-daemon" sauid=81 hostname=? addr=? terminal=?'UID="dbus" AUID="unset" SAUID="dbus"
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
The root cause for this is there is a rule to allow sending messages for all types in attribute *dbusd_unconfined*, but not the opposite rule:
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
# sesearch -A -s dbusd_unconfined -t sssd_t -c dbus
...
allow dbusd_unconfined sssd_t:dbus send_msg;
...
# sesearch -A -s sssd_t -t dbusd_unconfined -c dbus
... nothing related to "system_cronjob_t" ...
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
Version-Release number of selected component (if applicable):
selinux-policy-targeted-3.14.3-95.el8_6.4.noarch
How reproducible:
Always on customer system
Steps to Reproduce:
1. Have a SSSD client system
2. Create a system cronjob executing "sssctl"
~~~
# cat /etc/cron.d/check-sssd
* * * * * root /usr/sbin/sssctl domain-status -o <DOMAIN>
~~~
Actual results:
USER_AVC above
Expected results:
No USER_AVC and result
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 (selinux-policy bug fix and enhancement update), 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-2023:2965
Description of problem: We have a customer executing some sssd client command in a system cronjob (hence running as *system_cronjob_t*). We can see sssd cannot answer to the query due to a USER_AVC: -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- type=USER_AVC ... subj=system_u:system_r:system_dbusd_t:s0-s0:c0.c1023 msg='avc: denied { send_msg } for msgtype=method_return dest=:1.103521 ... scontext=system_u:system_r:sssd_t:s0 tcontext=system_u:system_r:system_cronjob_t:s0-s0:c0.c1023 tclass=dbus permissive=0 exe="/usr/bin/dbus-daemon" sauid=81 hostname=? addr=? terminal=?'UID="dbus" AUID="unset" SAUID="dbus" -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- The root cause for this is there is a rule to allow sending messages for all types in attribute *dbusd_unconfined*, but not the opposite rule: -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- # sesearch -A -s dbusd_unconfined -t sssd_t -c dbus ... allow dbusd_unconfined sssd_t:dbus send_msg; ... # sesearch -A -s sssd_t -t dbusd_unconfined -c dbus ... nothing related to "system_cronjob_t" ... -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- Version-Release number of selected component (if applicable): selinux-policy-targeted-3.14.3-95.el8_6.4.noarch How reproducible: Always on customer system Steps to Reproduce: 1. Have a SSSD client system 2. Create a system cronjob executing "sssctl" ~~~ # cat /etc/cron.d/check-sssd * * * * * root /usr/sbin/sssctl domain-status -o <DOMAIN> ~~~ Actual results: USER_AVC above Expected results: No USER_AVC and result