Silent Authentication must be removed from the Default Management Security Realm.

From JBoss EAP 6.3 Security Technical Implementation Guide

Part of SRG-APP-000033-AS-000024

Associated with: CCI-000213

SV-76713r1_rule Silent Authentication must be removed from the Default Management Security Realm.

Vulnerability discussion

Silent Authentication is a configuration setting that allows local OS users access to the JBoss server and a wide range of operations without specifically authenticating on an individual user basis. By default $localuser is a Superuser. This introduces an integrity and availability vulnerability and violates best practice requirements regarding accountability.

Check content

Log on to the OS of the JBoss server with OS permissions that allow access to JBoss. Using the relevant OS commands and syntax, cd to the /bin/ folder. Run the jboss-cli script. Connect to the server and authenticate. Verify that Silent Authentication has been removed from the default Management security realm. Run the following command. For standalone servers run the following command: "ls /core-service=management/securityrealm=ManagementRealm/authentication" For managed domain installations run the following command: "ls /host=HOST_NAME/core-service=management/securityrealm=ManagementRealm/authentication" If "local" is returned, this is a finding.

Fix text

Log on to the OS of the JBoss server with OS permissions that allow access to JBoss. Using the relevant OS commands and syntax, cd to the /bin/ folder. Run the jboss-cli script. Connect to the server and authenticate. Remove the local element from the Management Realm. For standalone servers run the following command: /core-service=management/securityrealm= ManagementRealm/authentication=local:remove For managed domain installations run the following command: /host=HOST_NAME/core-service=management/securityrealm= ManagementRealm/authentication=local:remove

Pro Tips

Lavender hyperlinks in small type off to the right (of CSS class id, if you view the page source) point to globally unique URIs for each document and item. Copy the link location and paste anywhere you need to talk unambiguously about these things.

You can obtain data about documents and items in other formats. Simply provide an HTTP header Accept: text/turtle or Accept: application/rdf+xml.

Powered by sagemincer