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:
SELinux policy for Tomcat should not allow access to rpm database by default


Version-Release number of selected component (if applicable):
selinux-policy-3.13.1-166.el7


How reproducible:
always


Steps to Reproduce:
1. From some application deployed in Tomcat application server attempt to
   access rpm database (initially observed on Spacewalk)


Actual results:
Application running in Tomcat is allowed to access rpm database


Expected results:
This should not be allowed (at least by default). When needed, should be allowed by application specific policy.


Additional info:
Opening this bug after discussion with Miroslav Grepl in bug 1451318.

Please attach SELinux denials that are triggered by your scenario.

# ausearch -m avc -m user_avc -m selinux_err -m user_selinux_err -i -ts today

Please see bug 1451318 for details. Problem here is policy allows something which should be denied.

(In reply to Jan Hutař from comment #2)
> Please see bug 1451318 for details. Problem here is policy allows something
> which should be denied.

I think it is a misinterpretation. Ii could be allowed by another way (a booelan maybe) and this bug is for a discussion of that from my point of view.

Is it OK?

Yep, I'm not against discussion. With comment #0 and comment #2 I just wanted to state the problem.

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-2018:0763