UCF STIG Viewer Logo

Warning and error messages displayed to clients must be modified to minimize the identity of the Apache web server, patches, loaded modules, and directory paths.


Overview

Finding ID Version Rule ID IA Controls Severity
V-214384 AS24-W2-000620 SV-214384r505106_rule Medium
Description
Information needed by an attacker to begin looking for possible vulnerabilities in a web server includes any information about the web server, backend systems being accessed, and plug-ins or modules being used. Web servers will often display error messages to client users displaying enough information to aid in the debugging of the error. The information given back in error messages may display the 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. This information could be used by an attacker to blueprint what type of attacks might be successful. The information given to users must be minimized to not aid in the blueprinting of the web server.
STIG Date
Apache Server 2.4 Windows Site Security Technical Implementation Guide 2021-09-27

Details

Check Text ( C-15595r505104_chk )
Review the <'INSTALLED PATH'>\conf\httpd.conf file.

If the "ErrorDocument" directive is not being used, this is a finding.
Fix Text (F-15593r505105_fix)
Edit the <'INSTALLED PATH'>\conf\httpd.conf file and use the "ErrorDocument" directive to enable custom error pages.

ErrorDocument 500 "Sorry, our script crashed. Oh dear"
ErrorDocument 500 /cgi-bin/crash-recover
ErrorDocument 500 http://error.example.com/server_error.html
ErrorDocument 404 /errors/not_found.html
ErrorDocument 401 /subscription/how_to_subscribe.html

The syntax of the ErrorDocument directive is:

ErrorDocument <3-digit-code>

Additional Information:

https://httpd.apache.org/docs/2.4/custom-error.html