Patch

CVE-2024-40725

with vRx

Vulnerability Overview

CVE Name

CVE-2024-40725

Severity

5.3

Medium

CVE Description

A partial fix for CVE-2024-39884 in the core of Apache HTTP Server 2.4.61 ignores some use of the legacy content-type based configuration of handlers. "AddType" and similar configuration, under some circumstances where files are requested indirectly, result...

Show less

Latest Patch info

There is no patch available at the moment, but you can use our script.

Patch Name

Date

Script

Script Type

Remediation script

Copy script

🔒 Mitigating CVE-2024-40725: Securing Apache from Source Code Disclosure This Bash script is designed to help protect your Apache HTTP Server from CVE-2024-40725, a vulnerability that can expose sensitive source code like PHP scripts. This issue stems from improper handling of the AddType directive in Apache configurations. 🔍 How it works: The script performs multiple steps to secure your Apache setup: Disables risky AddType and ForceType directives in Apache configurations, preventing raw code from being served instead of interpreted. Sets secure file permissions on sensitive files (like .php), ensuring that unauthorized users cannot read them. Creates .htaccess rules in critical directories to block access to files containing sensitive code. Disables directory listings to prevent potential attackers from exploring your directory structure. Restarts Apache to apply these changes effectively. ⚠️ Why it matters: CVE-2024-40725 exploits misconfigurations in older Apache versions (pre-2.4.62), allowing attackers to disclose local source code, which could lead to further exploitation. If you're running an affected Apache version, applying these mitigations can significantly reduce the risk of exposure while you plan your update to the patched version.

Read less

#!/bin/bash

# Disable AddType and ForceType directives in Apache config files
disable_directives() {
    config_files=("/etc/apache2/apache2.conf" "/etc/apache2/conf-available/*.conf" "/etc/apache2/sites-available/*.conf" "/etc/httpd/conf/httpd.conf")

for config_file in ${config_files[@]}; do
        if [[ -f $config_file ]]; then
            echo "Processing $config_file..."
            # Comment out AddType and ForceType lines
            sudo sed -i 's/^\s*$AddType\|ForceType$/# \1/g' $config_file
        fi
    done
    echo "Disabled AddType and ForceType directives."
}

# Set proper permissions for PHP and other sensitive files
set_file_permissions() {
    sensitive_dirs=("/var/www/html" "/your/custom/path")

for dir in ${sensitive_dirs[@]}; do
        if [[ -d $dir ]]; then
            echo "Setting file permissions in $dir..."
            # Set permission to 640 for PHP and other sensitive files
            sudo find $dir -type f $ -name "*.php" -o -name "*.conf" $ -exec chmod 640 {} \;
        fi
    done
    echo "File permissions have been set."
}

# Create .htaccess to deny access to sensitive files
deny_access_to_sensitive_files() {
    sensitive_dirs=("/var/www/html" "/your/custom/path")

for dir in ${sensitive_dirs[@]}; do
        if [[ -d $dir ]]; then
            echo "Creating .htaccess in $dir..."
            # Add .htaccess to deny direct access to sensitive files
            echo '<FilesMatch "\.php$">
Require all denied
</FilesMatch>' | sudo tee "$dir/.htaccess"
        fi
    done
    echo ".htaccess files created to block direct access to sensitive files."
}

# Disable directory listings in Apache
disable_directory_listings() {
    apache_conf="/etc/apache2/apache2.conf"  # CHANGE IF NEEDED
    if [[ ! -f "$apache_conf" ]]; then
        apache_conf="/etc/httpd/conf/httpd.conf"
    fi
    
    if [[ -f "$apache_conf" ]]; then
        echo "Disabling directory listings in Apache..."
        sudo sed -i 's/Options Indexes/Options -Indexes/g' "$apache_conf"
        echo "Directory listings disabled."
    else
        echo "Apache configuration file not found. Please verify the path."
    fi
}

# Restart Apache
restart_apache() {
    if systemctl status apache2.service > /dev/null 2>&1; then
        echo "Restarting Apache (apache2.service)..."
        sudo systemctl restart apache2
    elif systemctl status httpd.service > /dev/null 2>&1; then
        echo "Restarting Apache (httpd.service)..."
        sudo systemctl restart httpd
    else
        echo "Apache service not found. Please verify the service name."
    fi
}

disable_directives
set_file_permissions
deny_access_to_sensitive_files
disable_directory_listings
restart_apache

echo "All mitigations for CVE-2024-40725 have been applied."

Copy script

Affected OS & Apps

HTTP Server

Apache

4.8

Patch faster and smarter
with vRx

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

More than 600 customers trust vRx:

Solution

‍Remediate faster with vRx

Patch Management

vRx automatically deploys patches across all systems, cutting patching time by 80%.

Scripting Engine

vRx’s scripting engine solves complex vulnerabilities, like log4j, with built-in or custom scripts.

Patchless Protection

vRx’s Patchless Protection secures vulnerable apps and reduces risk while maintaining functionality.

Book a demo

4.9

4.8

4.9

Hear from our Customers

Valuable resources saved

"Before vRx, we would spend countless hours manually finding and verifying patches. We saved so much time (and headache!)."

Anonymous IT Operations Lead

IT Operations Lead

Third-party software patching is the most valuable feature.

"We have automated third-party patching on specific software, improving efficiency by 80%. vRx has reduced our patching time, which has improved our operations. It is more robust than other solutions because it offers better third-party remediation."

Billy Turner

VP, Managed Technology & Services

Single source of truth, capable of handling any application in our fleet

"vRx gives a single pane of glass to see what patches needed to go out and what sort of vulnerabilities we have on our Windows machines. Our meantime to remediate vulnerabilities has gone down by about 60% to 70%."

Peter Fallowfield

IT Manager

60% faster remediation, many hours saved

"Typically, with our previous solution of ManageEngine, it took about three hours to patch Windows Server, and now, that is less than an hour. It means less downtime for the business each month when we do patches."

Anonymous Security Analyst

Security Analyst

Great patching capabilities, helpful dashboard, and excellent support

"vRx has saved us an incredible amount of time. We can just rely on the automated system and the schedules we've set. It's a huge time saver. It's saved us hundreds of hours."

Michael Cortez

Sr. Director of IT

My favorite feature is Patchless Protection

"With Vicarius' vRx, I've never seen a patch that failed or had to be rolled back. We're saving quite a bit of time. Our clients using vRx haven't had any issues, and they've easily established patching for all their endpoints. "

Jeremy Herman

Security Engineer

Unified vulnerability discovery, prioritization, and remediation

"Vicarius streamlines vulnerability management between IT & Security by directly linking identified vulnerabilities to required patches, enhancing efficiency. The automation process has saved at least 30 percent of our manual tasks."

Wayne Ajimine

Information Security Professional

Patchless Protection is an incredible technology!

"vRx reduces the time customers spend on patching by reducing the overhead on the administrators, allowing them to do additional work. It saves time they would spend addressing the patching process, follow-ups, etc."

Antwune Gray

VP IT Security and Services