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.
+++ This bug was initially created as a clone of Bug #1758140 +++
+++ This bug was initially created as a clone of Bug #1599382 +++
Description of problem:
SELinux prevents aide from checking hundreds of files.
Version-Release number of selected component (if applicable):
aide-0.16-11.el8.x86_64
selinux-policy-3.14.3-20.el8.noarch
selinux-policy-targeted-3.14.3-20.el8.noarch
Steps to reproduce:
1) get a RHEL-8 machine (targeted policy is active)
2) initialize the AIDE database
# /usr/sbin/aide -c /etc/aide.conf --init
3) run the aide check via a cronjob
* * * * * root /usr/sbin/aide --check --config=/etc/aide.conf
Following errors appear in /var/log/aide/aide.log:
get_file_status: lstat() failed for /etc/udev/rules.d/.null: Permission denied
If /etc/aide.conf is unchanged then the scenario triggers following SELinux denial:
----
type=PROCTITLE msg=audit(10/03/2019 12:08:03.340:840) : proctitle=/usr/sbin/aide --check --config=/etc/aide.conf
type=SYSCALL msg=audit(10/03/2019 12:08:03.340:840) : arch=x86_64 syscall=lstat success=no exit=EACCES(Permission denied) a0=0x5579f6da6870 a1=0x7ffdb3fa60d0 a2=0x7ffdb3fa60d0 a3=0x17 items=0 ppid=12405 pid=12407 auid=root uid=root gid=root euid=root suid=root fsuid=root egid=root sgid=root fsgid=root tty=(none) ses=33 comm=aide exe=/usr/sbin/aide subj=system_u:system_r:aide_t:s0-s0:c0.c1023 key=(null)
type=AVC msg=audit(10/03/2019 12:08:03.340:840) : avc: denied { getattr } for pid=12407 comm=aide path=/etc/udev/rules.d/.null dev="vda1" ino=732146 scontext=system_u:system_r:aide_t:s0-s0:c0.c1023 tcontext=system_u:object_r:udev_rules_t:s0 tclass=chr_file permissive=0
----
If /etc/aide.conf is modified in such a way that /dev/ is checked, then hundreds of SELinux denials are triggered.
Radovan,
Does it make sense that AIDE is checking also /dev ?
Because aide is executed via cronjob, it's ends in aide_t SELinux domain and in aide policy it's not allowed to scan /dev.
Thanks,
Lukas.
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-2020:1773