| name | cis-apache-2.6 |
| description | Ensure the Proxy Modules Are Disabled |
| category | cis-apache |
| version | 3.6.0 |
| author | cyberstrike-official |
| tags | ["cis","apache","linux","modules","proxy"] |
| cis_id | 2.6 |
| cis_benchmark | CIS Apache HTTP Server 2.2 Benchmark v3.6.0 |
| tech_stack | ["linux","apache"] |
| cwe_ids | [] |
| chains_with | [] |
| prerequisites | [] |
| severity_boost | {} |
Ensure the Proxy Modules Are Disabled
Description
The Apache proxy modules allow the server to act as a proxy (either forward or reverse proxy) for HTTP and other protocols with additional proxy modules loaded. If the Apache installation is not intended to proxy requests to or from another network, the proxy module should not be loaded.
Rationale
Proxy servers can act as an important security control when properly configured. However, a secure proxy server is not within the scope of this benchmark. A web server should be primarily a web server or a proxy but not both, for the same reasons that other multi-use servers are not recommended. Scanning for web servers that will also proxy requests is a very common attack because proxy servers are useful for anonymizing attacks on other servers, or possibly proxying requests into an otherwise protected network.
Impact
None documented
Audit Procedure
Perform the following to determine if the proxy modules are disabled.
Run the httpd server with the -M option to list enabled modules:
Note: If the modules are correctly disabled, the only output when executing the above command should be Syntax OK.
Remediation
Perform either one of the following to disable the proxy modules:
- For source builds with static modules, run the Apache
./configure script without including the mod_proxy and all other proxy modules in the --enable-modules=configure script options.
$ cd $DOWNLOAD/httpd-2.2.22
$ ./configure
- For dynamically loaded modules, comment out or remove the
LoadModule directive for the mod_proxy module and all other proxy modules from the httpd.conf file.