brunexgeek/mod_bouncer

Apache2 module to block requests via pattern matching.

mod_bouncer

mod_bouncer is a module for Apache 2.4 that blocks incoming requests containing specific patterns in their URL path. Blocked requests can be sent to a log file, enabling external tools (e.g. fail2ban) to set firewall rules to completely block attackers or generate alerts.

Build and install

You need the APXS tool to build and install the module.

Use the script build.sh to build the module and install.sh to install and activate the module in your Apache installation. Make sure you have the necessary privileges to use install.sh.

# ./build.sh
# sudo ./install.sh

You need to restart the Apache service after the installation.

Configuration

mod_bouncer offers the following directives to be used in the server configuration.

• BouncerEngine: Enable (on) or disable (off) the mod_bouncer. This directive should appear before any other. By default the mod_bouncer is disabled.
• BouncerPattern: Add one or more patterns. Patterns are separated by spaces and must be 3 to 255 characters long. Valid characters are (see section 2. Characters of RFC 3986): A-Z, a-z, 0-9, -, ., _, ~, :, /, ?, #, [, ], @, !, $, &, ', (, ), *, +, ,, ;, %, and =. You can also use ^ as the first character to indicate the pattern must appear at the beginning of the URL path. This directive can be used multiple times.
• BouncerPatternFile: Add patterns via external text file. Each line of the file is equivalent to a BouncerPattern directive. This directive can be used multiple times.
• BouncerTrustedProxy: List of trusted proxies IP addresses. This list is used to find out the internet address of the client when Apache is behind one or more internal proxies. For more accurate results, each internal proxy in the chain should appear here. This directive can be used multiple times. For more information, see X-Forwarded-For at MDN. The address discovered is shown in the log along with the current client address (probably from an internal proxy).
• BouncerLog: Path to the log file. Make sure the Apache process has the necessary privilege to write to the file. This log contains entries for every blocked request and can be monitored by tools (e.g. fail2ban) to change firewall rules or generate alerts.

Pattern file

The pattern file, used by the BouncerPatternFile directive, specifies a set of patterns. This file is especially useful for sharing patterns between virtual hosts. Each line in the file is equivalent to a BouncerPattern directive.

The first argument of each pattern is a set of HTTP methods to which the pattern will be applied. More than one method can be specified, separating them with vertical bars (|). Possible values are one or more of: GET, POST, PUT, DELETE, CONNECT, OPTIONS, TRACE and PATCH. The special value ANY can be used to match all HTTP methods.

GET|POST /xmlrpc cgi-bin
POST /changeUser /delete_file
ANY virus

Example

Example of server at 10.0.1.25 that receives requests through a proxy at 10.0.1.24:

<VirtualHost 10.0.1.25:80>
    ...
    <IfModule mod_bouncer.c>
            BouncerEngine on
            BouncerPattern GET|POST .git ^/wp-admin
            BouncerPattern ^/xmlrpc
            BouncerLog /run/mod_bouncer.log
            BouncerTrustedProxy 10.0.1.24
            BouncerPatternFile mod_bouncer.txt
    </IfModule>
    ...
</VirtualHost>

Example of output for blocked request in /run/mod_bouncer.log. The address 200.10.3.22 in the example was extracted from X-Forwarded-For header since 10.0.1.24 is a trusted proxy.

2022-05-10T09:28:40-0400 [BLOCKED] 10.0.1.24 200.10.3.22 GET "/wp-admin/ps" 404 "" "curl/7.68.0"