Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1491039 - SELinux denies name_bind to jboss_management_port_t for tomcat_t
SELinux denies name_bind to jboss_management_port_t for tomcat_t
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: selinux-policy (Show other bugs)
7.4
All Linux
unspecified Severity unspecified
: rc
: ---
Assigned To: Lukas Vrabec
Milos Malik
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-09-12 16:59 EDT by Robert Bost
Modified: 2018-04-10 08:42 EDT (History)
5 users (show)

See Also:
Fixed In Version: selinux-policy-3.13.1-175.el7
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-04-10 08:42:01 EDT
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)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 3180911 None None None 2017-09-12 17:40 EDT
Red Hat Product Errata RHBA-2018:0763 None None None 2018-04-10 08:42 EDT

  None (edit)
Description Robert Bost 2017-09-12 16:59:35 EDT
SELinux is denying tomcat from binding to port 9999 for JMX, with the following AVC denial in /var/log/audit.log

type=AVC msg=audit(1505248782.641:3017): avc:  denied  { name_bind } for  pid=10189 comm="java" src=9999 scontext=system_u:system_r:tomcat_t:s0 tcontext=system_u:object_r:jboss_management_port_t:s0 tclass=tcp_socket

This worked without issue in previous versions of the targeted policy.


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

How reproducible:
Always

Steps to Reproduce:
1. Create a new RHEL 7.4 machine
2. yum install tomcat
3. Add the following to /etc/sysconfig/tomcat
JAVA_OPTS="-Dcom.sun.management.jmxremote.port=9999 -Dcom.sun.management.jmxremote.rmi.port=9999 -Dcom.sun.management.jmxremote=true -Dcom.sun.management.jmxremote.local.only=false -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false "
4. systemctl start tomcat.service

Actual results:
AVC denial

Expected results:
A successful bind, like previous versions of the policy.
Comment 2 Robert Bost 2017-09-12 17:01:54 EDT
I think port 9999 is meant to be the JMX port for Java applications.
Comment 7 errata-xmlrpc 2018-04-10 08:42:01 EDT
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

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