Details

Information needed by an attacker to begin looking for possible vulnerabilities in a web server includes any information about the web server and plug-ins or modules being used. When debugging or trace information is enabled in a production web server, information about the web server, such as web server type, version, patches installed, plug-ins and modules installed, type of code being used by the hosted application, and any backends being used for data storage may be displayed. Since this information may be placed in logs and general messages during normal operation of the web server, an attacker does not need to cause an error condition to gain this information.

The Security Token Service can be configured to set the debugging level. By setting the debugging level to zero, no debugging information will be provided to a malicious user.

Solution

Navigate to and open /usr/lib/vmware-sso/vmware-sts/conf/web.xml.

Navigate to all nodes that are not set to ‘0’.

Set the to ‘0’ in alldebug nodes.

Note: The debug setting should look like the following:

debug0

Supportive Information

The following resource is also helpful.

• https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_VMW_vSphere_6-7_STIG.zip

This security hardening control applies to the following category of controls within NIST 800-53: System and Information Integrity.This control applies to the following type of system Unix.

References

• 800-53|SI-11a.
• CAT|II
• CCI|CCI-001312
• Rule-ID|SV-239677r679103_rule
• STIG-ID|VCST-67-000026
• Vuln-ID|V-239677

Source

• Tenable.com/audits