OHS must have the HeaderName directive disabled.
From Oracle HTTP Server 12.1.3 Security Technical Implementation Guide
Part of SRG-APP-000141-WSR-000075
Associated with:
CCI-000381
SV-78767r1_rule
OHS must have the HeaderName directive disabled.
Vulnerability discussion
A web server can provide many features, services, and processes. Some of these may be deemed unnecessary or too unsecure to run on a production DoD system. The web server must provide the capability to disable, uninstall, or deactivate functionality and services that are deemed to be non-essential to the web server mission or can adversely impact server performance.
Check content
1. Open $DOMAIN_HOME/config/fmwconfig/components/OHS//httpd.conf and every .conf file (e.g., ssl.conf) included in it with an editor that contains a "HeaderName" directive.
2. Search for a "HeaderName" directive at the OHS server, virtual host, and directory configuration scopes.
3. If the directive exists and is not commented out, this is a finding.
Fix text
1. Open $DOMAIN_HOME/config/fmwconfig/components/OHS//httpd.conf and every .conf file (e.g., ssl.conf) included in it with an editor that contains a "HeaderName" directive.
2. Search for a "HeaderName" directive at the OHS server, virtual host, and directory configuration scopes.
3. Comment out the "HeaderName" directive if it exists.
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