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:
Default fapolicyd rule set prevents file access by /usr/bin/perl Process is not caught as a perl, though, thus falsely allowing the access. 

Version-Release number of selected component (if applicable):
fapolicyd-0.8.10-3.el8.x86_64

How reproducible:
reliable

Steps to Reproduce:
1.
[root@localhost ~]# grep perl /etc/fapolicyd/fapolicyd.rules 
# Block all perl
deny_audit exe=/usr/bin/perl all
#allow all dir=execdirs ftype=text/x-perl
#deny_audit all ftype=text/x-perl

2. fapolicyd --debug (in one window)
3. /usr/bin/perl -e'print $$;open F, "./ahoj" or die'

Actual results:
fapolicyd --debug reports "rule:18 dec=allow auid=1000 pid=5783 exe=/usr/bin/bash file=/home/admin/ahoj"

perl command returns same PID

Expected results:
Command is properly disrupted and identified as perl 

Additional info:

This is caused by bad cache management. The latest upstream release should work as expected because it hooks the fanotify EXEC_PERM kernel option to correctly delete the bash cache entry.

Assuming that you have qt5-qtbase-devel installed, an appropriate test would be:

/usr/bin/syncqt.pl --help

That should be denied by rule 23.

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/RHEA-2020:1687