# CVE-2024-10306: Mod_proxy_cluster: mod_proxy_cluster unauthorized mcmp requests > Attackers can send unauthorized MCMP requests to add, remove, or update load-balancing nodes due to incorrect Apache directive usage. - **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 23 Apr 2025 - **Updated:** 21 Oct 2026 - **Also known as:** ALSA-2025:9434, ALSA-2025:9466, GHSA-jm2g-3f56-rvvh, RHBA-2025:2973, RHBA-2025:5309, RHSA-2025:9434, RHSA-2025:9466, RHSA-2025:9997, RLSA-2025:9434, RLSA-2025:9466 ## What is CVE-2024-10306? CVE-2024-10306 is a medium-severity missing authorization vulnerability in Red Hat Enterprise Linux 10, published on 23 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description A vulnerability was found in mod_proxy_cluster. The issue is that the directive should be replaced by the 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. Weakness: CWE-863 (Incorrect Authorization) ## Which versions are affected by CVE-2024-10306? | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `mod_proxy_cluster` | AlmaLinux:10 | All versions | 1.3.22-1.el10_0.2 | | `mod_proxy_cluster` | AlmaLinux:9 | All versions | 1.3.22-1.el9_6.1 | | `mod_proxy_cluster` | Red Hat:enterprise_linux:10.0 | All versions | 0:1.3.21-1.el10 | | `mod_proxy_cluster` | Red Hat:enterprise_linux:10.0 | All versions | 0:1.3.22-1.el10_0.2 | | `mod_proxy_cluster-debuginfo` | Red Hat:enterprise_linux:10.0 | All versions | 0:1.3.21-1.el10 | | `mod_proxy_cluster-debuginfo` | Red Hat:enterprise_linux:10.0 | All versions | 0:1.3.22-1.el10_0.2 | | `mod_proxy_cluster-debugsource` | Red Hat:enterprise_linux:10.0 | All versions | 0:1.3.21-1.el10 | | `mod_proxy_cluster-debugsource` | Red Hat:enterprise_linux:10.0 | All versions | 0:1.3.22-1.el10_0.2 | | `mod_proxy_cluster` | Red Hat:enterprise_linux:9::appstream | All versions | 0:1.3.22-1.el9_5.2 | | `mod_proxy_cluster` | Red Hat:enterprise_linux:9::appstream | All versions | 0:1.3.22-1.el9_6.1 | | `mod_proxy_cluster-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:1.3.22-1.el9_5.2 | | `mod_proxy_cluster-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:1.3.22-1.el9_6.1 | | `mod_proxy_cluster-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:1.3.22-1.el9_5.2 | | `mod_proxy_cluster-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:1.3.22-1.el9_6.1 | | `mod_proxy_cluster` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:1.3.22-1.el9_4.1 | | `mod_proxy_cluster-debuginfo` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:1.3.22-1.el9_4.1 | | `mod_proxy_cluster-debugsource` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:1.3.22-1.el9_4.1 | | `mod_proxy_cluster` | Rocky Linux:10 | All versions | 0:1.3.22-1.el10_0.2 | | `mod_proxy_cluster` | Rocky Linux:9 | All versions | 0:1.3.22-1.el9_6.1 | ## How do I fix CVE-2024-10306? Apply the vendor's patch. ## Is CVE-2024-10306 being exploited? There is no known exploitation of CVE-2024-10306 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-10306 and fix it if it is affected. What it is: CVE-2024-10306 is a medium-severity missing authorization vulnerability in Red Hat Enterprise Linux 10, published on 23 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2024-10306 in the wild and no public exploit code. Affected product: Red Hat Enterprise Linux 10. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-10306/ (Markdown: https://insights.sbomify.com/CVE-2024-10306/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-10306 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-10306 - OSV: https://osv.dev/vulnerability/CVE-2024-10306 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-10306/ Summaries are generated and may contain mistakes; the official description above is the record.