OpenControls Logo

STIG Viewer

STIGViewer Support

The Apache web server cookies, such as session cookies, sent to the client using SSL/TLS must not be compressed.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-214301AS24-U2-000870SV-214301r961632_ruleCCI-002448medium
Description
A cookie is used when a web server needs to share data with the client's browser. The data is often used to remember the client when the client returns to the hosted application at a later date. A session cookie is a special type of cookie used to remember the client during the session. The cookie will contain the session identifier (ID) and may contain authentication data to the hosted application. To protect this data from easily being compromised, the cookie can be encrypted. When a cookie is sent encrypted via SSL/TLS, an attacker must spend a great deal of time and resources to decrypt the cookie. If, along with encryption, the cookie is compressed, the attacker can now use a combination of plaintext injection and inadvertent information leakage through data compression to reduce the time needed to decrypt the cookie. This attack is called Compression Ratio Info-leak Made Easy (CRIME). Cookies shared between the Apache web server and the client when encrypted should not also be compressed.
STIGDate
Apache Server 2.4 UNIX Site Security Technical Implementation Guide2025-02-12

Related Frameworks

1 mapping across 3 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (1) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

CRY-09.2Asymmetric Keys
1.00
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (12) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

AC-17(2)Protection of Confidentiality and Integrity Using Encryption
1.00
AC-3Access Enforcement
1.00
IA-5(1)Password-based Authentication
1.00
IA-7Cryptographic Module Authentication
1.00
PE-3Physical Access Control
1.00
SA-9(5)Processing, Storage, and Service Location
1.00
SC-12(3)Asymmetric Keys
1.00
SC-13Cryptographic Protection
1.00
SC-15(3)Disabling and Removal in Secure Work Areas
1.00
SC-15(4)Explicitly Indicate Current Participants
1.00

+2 more (top 10 by confidence shown)

CCI1 mapping
CCI-002448
1.00

Details

Check Text (C-214301r961632_chk)

In a command line, run "httpd -M | grep -i ssl_module". If "ssl_module" is not listed, this is a finding. Determine the location of the "HTTPD_ROOT" directory and the "httpd.conf" file: # apachectl -V | egrep -i 'httpd_root|server_config_file' -D HTTPD_ROOT="/etc/httpd" -D SERVER_CONFIG_FILE="conf/httpd.conf" Note: The apachectl front end is the preferred method for locating the Apache httpd file. For some Linux distributions "apache2ctl -V" or "httpd -V" can also be used. If the "SSLCompression" directive does not exist or is set to "on", this is a finding.

Fix Text (F-15512r881515_fix)

Determine the location of the "HTTPD_ROOT" directory and the "httpd.conf" file: # apachectl -V | egrep -i 'httpd_root|server_config_file' -D HTTPD_ROOT="/etc/httpd" -D SERVER_CONFIG_FILE="conf/httpd.conf" Ensure the "SSLCompression" is added and looks like the following: SSLCompression off Restart Apache: apachectl restart