Bug 1477948

Summary:	in bug 1451318, Tomcat was allowed to connect to PostgreSQL port, but there should be a boolean for that
Product:	Red Hat Enterprise Linux 7	Reporter:	Jan Hutař <jhutar>
Component:	selinux-policy	Assignee:	Lukas Vrabec <lvrabec>
Status:	CLOSED ERRATA	QA Contact:	Milos Malik <mmalik>
Severity:	medium	Docs Contact:	Mirek Jahoda <mjahoda>
Priority:	unspecified
Version:	7.4	CC:	lvrabec, mgrepl, mmalik, plautrba, pvrabec, ssekidde, zpytela
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Release Note
Doc Text:	A new SELinux boolean called tomcat_can_network_connect_db was introduced so that system administrator can decide if such use case should be allowed or not.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-10-30 10:01:27 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1477960

Description Jan Hutař 2017-08-03 09:50:39 UTC

Description of problem:
In bug 1451318, Tomcat was allowed to connect to PostgreSQL port, but there should be a boolean for that


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


How reproducible:
always


Steps to Reproduce:
1. Try to access PostgreSQL from application running in Tomcat
   (for me it was Spacewalk)


Actual results:
Application running in Tomcat is allowed to access PostgreSQL by default


Expected results:
This should not be allowed by default. Apache also have extra boolean:

$ getsebool -a | grep httpd
[...]
httpd_can_network_connect --> off
[...]
httpd_can_network_connect_db --> off
[...]


Additional info:
It was implemented in bug 1451318 and this bug is a sibling of bug 1477887.

Comment 5 errata-xmlrpc 2018-10-30 10:01:27 UTC

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:3111