Bug 1477948 - in bug 1451318, Tomcat was allowed to connect to PostgreSQL port, but there should be a boolean for that
in bug 1451318, Tomcat was allowed to connect to PostgreSQL port, but there s...
Status: NEW
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: selinux-policy (Show other bugs)
7.4
All Linux
unspecified Severity medium
: rc
: ---
Assigned To: Lukas Vrabec
Milos Malik
:
Depends On:
Blocks: 1477960
  Show dependency treegraph
 
Reported: 2017-08-03 05:50 EDT by Jan Hutař
Modified: 2017-08-17 10:08 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jan Hutař 2017-08-03 05:50:39 EDT
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.

Note You need to log in before you can comment on or make changes to this bug.