LiveActive security incident?Get immediate response
CVE Record

CVE-2024-10306: Mod_proxy_cluster: mod_proxy_cluster unauthorized mcmp requests

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.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2024-10306 is an access-control flaw in mod_proxy_cluster. A configuration pattern using <Directory> may not restrict MCMP management requests as intended, letting a user with network access to the host alter load-balancer node state. Red Hat rates it medium; the host should not be public-facing.

Executive priority

Treat as a targeted infrastructure-hardening issue, not an emergency internet-wide crisis based on current evidence. Prioritize systems where load-balancer management interfaces are reachable by untrusted users or networks.

Technical view

The issue is CWE-863: incorrect authorization. The documented problem is that <Directory> should be replaced by <Location> for MCMP access restrictions, because Require ip may not apply as expected. Unauthorized MCMP requests could add, remove, or update backend nodes, causing limited confidentiality and integrity impact without availability impact in the CVSS vector.

Likely exposure

Exposure is most likely in environments running mod_proxy_cluster on affected Red Hat Enterprise Linux 9, RHEL 10, or Red Hat JBoss Core Services packages, especially where the MCMP management endpoint is reachable beyond trusted administrative networks.

Exploitation context

The CVSS vector requires network access and low privileges, with no user interaction. The source bundle does not indicate CISA KEV listing or active exploitation. Public exposure would increase concern, but Red Hat notes this host should not serve general public traffic.

Researcher notes

Key uncertainty is exact fixed-version mapping across Red Hat streams from the provided bundle. The root cause is configuration-scope mismatch, not a memory corruption issue. Validate effective authorization behavior without publishing offensive request details.

Mitigation direction

  • Apply applicable Red Hat updates from the listed RHSA and RHBA advisories.
  • Review vendor guidance for affected mod_proxy_cluster and JBoss Core Services packages.
  • Replace vulnerable <Directory>-based MCMP restrictions with vendor-recommended <Location>-based controls.
  • Restrict MCMP management access to trusted administrative networks only.
  • Ensure the management host is not exposed to the public internet.

Validation and detection

  • Inventory systems for mod_proxy_cluster and JBoss Core Services packages.
  • Compare installed package versions against Red Hat advisories for your platform.
  • Review Apache configuration for MCMP access controls using <Directory>.
  • Confirm MCMP endpoints are reachable only from trusted networks.
  • Check monitoring for unexpected backend node add, remove, or update activity.
Prepared
Confidence
high
Sources
9

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-863: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-10306 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
5Timeline events
1ADP providers
9Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N2.82.5redhat

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2024-10306Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. Source timelineredhat

    Reported to Red Hat.

  2. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  3. Source timelineredhat

    Made public.

  4. CVE publishedCVE Program

    The CVE record was published.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Unknown vendormod_proxy_clustermod_proxy_cluster, 1.3.17unaffected
Red HatRed Hat Enterprise Linux 10mod_proxy_cluster, 0:1.3.21-1.el10affected
Red HatRed Hat Enterprise Linux 10mod_proxy_cluster, 0:1.3.22-1.el10_0.2affected
Red HatRed Hat Enterprise Linux 9mod_proxy_cluster, 0:1.3.22-1.el9_5.2affected
Red HatRed Hat Enterprise Linux 9mod_proxy_cluster, 0:1.3.22-1.el9_6.1affected
Red HatRed Hat Enterprise Linux 9.4 Extended Update Supportmod_proxy_cluster, 0:1.3.22-1.el9_4.1affected
Red HatRed Hat JBoss Core Servicesjbcs-httpd24-mod_proxy_clusteraffected
Red HatRed Hat JBoss Core Servicesmod_proxy_clusteraffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-863 · source CWE mapping

Incorrect Authorization

Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.