APACHE 2.2 Server for Windows STIG Version Comparison

There are 8 differences between versions v1 r11 (July 28, 2017) (the "left" version) and v1 r13 (Jan. 25, 2019) (the "right" version).

Check WA000-WWA056 W22 was changed between these two versions. Green, underlined text was added, red, struck-out text was removed.

The regular view of the left check and right check may be easier to read.

Title

The MultiViews directive must be disabled.

Check Content

Locate the Apache httpd.conf file. Open the httpd.conf file with an editor such as Notepad, and search for all occurrences of the following uncommented directive: Options Review Options. This check validates occurrences of the Options directive which are uncommented. Review all uncommented Options statements for "-MultiViews"and validate a preceding "-" to the following value: -MultiViews If MultiViews option exists. If the value is found on the Options statement, and it does not have a preceding "-", this is a finding. finding. If If the value does not exist at all, this would be a finding unless the enabled Options statement is set to “None”. "none".

Discussion

Directory options directives Apache HTTPD supports content negotiation as described in the HTTP/1.1 specification. It can choose the best representation of a resource based on the browser-supplied preferences for media type, languages, character set and encoding. It also implements a couple of features to give more intelligent handling of requests from browsers that send incomplete negotiation information. Content negotiation, or more accurately content selection, is the selection of the document that best matches the clients capabilities, from one of several available documents. There are directives that two implementations of this. • A type map (a file with the handler type-map) which explicitly lists the files containing the variants. • A Multiviews search (enabled by the Multiviews Options), where the server does an implicit filename pattern match, and choose from amongst the results. A MultiViews search is where the server does an implicit filename pattern match, and chooses from the results. For example, if you have a file called configuration.php (or other extension) in root folder and you set up a rule in your htaccess for a virtual folder called configuration/ then you'll have a problem with your rule because the server will choose configuration.php automatically if MultiViews is enabled. An attacker can be applied use the MultiViews functionality to aid in finding hidden file processes on the directory and potentially gather further sensitive information. MultiViews restrict access to file and directories. MultiViews is a per-directory option, meaning it can be set set, or explicitly disabled, with an Options directive within a <Directory>, <Location> or <Files> section in httpd.conf, or (if AllowOverride is properly set) in .htaccess files. To explicitly disable an Options functionality, the option must be listed on every uncommented Options directive with a preceding the option. The "-" preceding the option configures Apache to explicitly disable the option. An Options directive with "none" will also disable the functionality. If the option is listed on an Options directive line without a preceding - or without anything preceding it or with a "+" preceding it or not configured at all, the MultiViews option is enabled and is vulnerable.

Fix

Add a "-" to the MultiViews setting, or set the options directive to None.