JBoss must utilize encryption when using LDAP for authentication.

From JBoss EAP 6.3 Security Technical Implementation Guide

Associated with: CCI-000197

SV-76783r1_rule JBoss must utilize encryption when using LDAP for authentication.

Vulnerability discussion

Passwords need to be protected at all times, and encryption is the standard method for protecting passwords during transmission.Application servers have the capability to utilize LDAP directories for authentication. If LDAP connections are not protected during transmission, sensitive authentication credentials can be stolen. When the application server utilizes LDAP, the LDAP traffic must be encrypted.

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. Run the following command: For standalone servers: "ls /socket-binding-group=standard-sockets/remote-destination-outbound-socket-binding=ldap_connection" For managed domain installations: "ls /socket-binding-group=/remote-destination-outbound-socket-binding=" The default port for secure LDAP is 636. If 636 or secure LDAP protocol is not utilized, this is a finding.

Fix text

Follow steps in section 11.8 - Management Interface Security in the JBoss_Enterprise_Application_Platform-6.3-Administration_and_Configuration_Guide-en-US document. 1. Create an outbound connection to the LDAP server. 2. Create an LDAP-enabled security realm. 3. Reference the new security domain in the Management Interface.

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.