First published: Wed Oct 23 2024(Updated: )
A vulnerability was found in mod_proxy_cluster. The issue is that the <Directory> directive should be replaced by the <Location> directive as the former does not restrict IP/host access as `Require ip IP_ADDRESS` would suggest. This means that anyone with access to the host might send MCMP requests that may result in adding/removing/updating nodes for the balancing. However, this host should not be accessible to the public network as it does not serve the general traffic.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Apache mod_proxy_cluster |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-10306 is considered a critical vulnerability due to the risk of unauthorized access through improper IP/host access restriction.
To fix CVE-2024-10306, replace the <Directory> directive with the <Location> directive in your Apache mod_proxy_cluster configuration.
The potential impacts of CVE-2024-10306 include unauthorized users gaining access to server resources, leading to data exposure and security breaches.
CVE-2024-10306 affects all versions of Apache mod_proxy_cluster that utilize the <Directory> directive without proper access control.
A potential workaround for CVE-2024-10306 is to ensure that access controls are properly configured, although replacing the directive is the recommended solution.