← Back to Oracle HTTP Server 12.1.3 Security Technical Implementation Guide

V-221438

CAT II (Medium)

OHS must restrict access methods.

Rule ID

SV-221438r961863_rule

STIG

Oracle HTTP Server 12.1.3 Security Technical Implementation Guide

Version

V2R3

CCIs

CCI-000366

Discussion

The directive "<LimitExcept>" allows the system administrator to restrict what users may use which methods. An example of methods would be GET, POST and DELETE. These three are the most common used by applications and should be allowed. Methods such as TRACE, if allowed, give an attacker a way to map the system so that vulnerabilities to the system can be researched and developed.

Check Content

1. Open $DOMAIN_HOME/config/fmwconfig/components/OHS/<componentName>/httpd.conf and every .conf file (e.g., ssl.conf) included in it with an editor.

2. Search for the "<LimitExcept>" directive at the directory configuration scope.

3. If the "<LimitExcept>" directive is omitted (with the exception of the "<Directory />" directive) or is set improperly, this is a finding.

Fix Text

1. Open $DOMAIN_HOME/config/fmwconfig/components/OHS/<componentName>/httpd.conf and every .conf file (e.g., ssl.conf) included in it with an editor.

2. Search for the "<LimitExcept>" directive at the directory configuration scope.

3. Set the "<LimitExcept>" directive to "GET POST", add the directive if it does not exist.

4. Within the "<LimitExcept GET POST>" directives, add the directive "Deny" and set it to "from all".