The Apache web server must generate unique session identifiers that cannot be reliably reproduced.

From Apache Server 2.4 Windows Site Security Technical Implementation Guide

Associated with: CCI-001188

AS24-W2-000500_rule The Apache web server must generate unique session identifiers that cannot be reliably reproduced.

Vulnerability discussion

Communication between a client and the web server is done using the HTTP protocol, but HTTP is a stateless protocol. To maintain a connection or session, a web server will generate a session identifier (ID) for each client session when the session is initiated. The session ID allows the web server to track a user session and, in many cases, the user, if the user previously logged on to a hosted application.By being able to guess session IDs, an attacker can easily perform a man-in-the-middle attack. To truly generate random session identifiers that cannot be reproduced, the web server session ID generator, when used twice with the same input criteria, must generate an unrelated random ID.The session ID generator also needs to be a FIPS 140-2 approved generator.

Check content

Review the <'INSTALLED PATH'>\conf\httpd.conf file. Verify the "mod_unique_id" is loaded. If it does not exist, this is a finding.

Fix text

Edit the <'INSTALLED PATH'>\conf\httpd.conf file and load the "mod_unique_id" module. Restart Apache.

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.