LiveActive security incident?Get immediate response
CVE Record

CVE-2024-36401: Remote Code Execution (RCE) vulnerability in evaluating property name expressions in Geoserver

GeoServer is an open source server that allows users to share and edit geospatial data. Prior to versions 2.22.6, 2.23.6, 2.24.4, and 2.25.2, multiple OGC request parameters allow Remote Code Execution (RCE) by unauthenticated users through specially crafted input against a default GeoServer installation due to unsafely evaluating property names as XPath expressions. The GeoTools library API that GeoServer calls evaluates property/attribute names for feature types in a way that unsafely passes them to the commons-jxpath library which can execute arbitrary code when evaluating XPath expressions. This XPath evaluation is intended to be used only by complex feature types (i.e., Application Schema data stores) but is incorrectly being applied to simple feature types as well which makes this vulnerability apply to **ALL** GeoServer instances. No public PoC is provided but this vulnerability has been confirmed to be exploitable through WFS GetFeature, WFS GetPropertyValue, WMS GetMap, WMS GetFeatureInfo, WMS GetLegendGraphic and WPS Execute requests. This vulnerability can lead to executing arbitrary code. Versions 2.22.6, 2.23.6, 2.24.4, and 2.25.2 contain a patch for the issue. A workaround exists by removing the `gt-complex-x.y.jar` file from the GeoServer where `x.y` is the GeoTools version (e.g., `gt-complex-31.1.jar` if running GeoServer 2.25.1). This will remove the vulnerable code from GeoServer but may break some GeoServer functionality or prevent GeoServer from deploying if the gt-complex module is needed.

CriticalCVSS 9.8Known exploitedUpdated
Glexia's TakeHuman reviewedcritical

Security readout for executives and security teams

Plain-English summary

GeoServer can let an unauthenticated remote attacker run code on the server. The flaw affects default installations because property names are evaluated unsafely as XPath expressions. CISA lists this CVE in KEV, so exploitation has occurred. Treat internet-exposed GeoServer as an urgent remediation item.

Executive priority

Prioritize emergency remediation for any internet-facing GeoServer. This is unauthenticated remote code execution with known exploitation and full confidentiality, integrity, and availability impact. Internal-only systems still need rapid patching because compromise can provide a foothold into geospatial data services and connected infrastructure.

Technical view

GeoServer calls GeoTools, which can pass feature property names into commons-jxpath for XPath evaluation. That evaluation can execute arbitrary code and was incorrectly applied beyond complex feature types, making all GeoServer instances in the affected ranges vulnerable. Confirmed request surfaces include WFS, WMS, and WPS operations.

Likely exposure

Exposure is likely wherever GeoServer runs versions before 2.22.6, 2.23.6, 2.24.4, or 2.25.2. Public OGC endpoints increase urgency, but the advisory states the issue applies to all GeoServer instances, not only deployments using Application Schema data stores.

Exploitation context

CISA KEV inclusion confirms known exploitation. The source bundle says exploitation was confirmed through several OGC request types, but provides no public PoC details. No exploit workflow should be needed for triage; version and endpoint exposure are enough to prioritize response.

Researcher notes

Evidence is strong for affected versions, root cause, request families, patch versions, workaround, and KEV status. The provided sources do not include safe detection signatures or complete exploitation telemetry. Validate by version, module presence, network exposure, and logs rather than attempting exploit reproduction.

Mitigation direction

  • Upgrade GeoServer to 2.22.6, 2.23.6, 2.24.4, 2.25.2, or later supported releases.
  • If upgrade is delayed, evaluate removing the matching gt-complex jar as the documented workaround.
  • Test the workaround first; it may break complex feature functionality or prevent deployment.
  • Restrict public access to GeoServer OGC endpoints until patched.
  • Review vendor advisories for any newer release-specific guidance.

Validation and detection

  • Inventory all GeoServer deployments and record exact versions.
  • Confirm whether WFS, WMS, and WPS endpoints are reachable from untrusted networks.
  • Verify patched versions are deployed after remediation.
  • Check whether gt-complex remains installed on unpatched systems.
  • Review GeoServer logs for unusual OGC requests and unexpected server-side execution indicators.
Prepared
Reviewed
Confidence
high
Sources
6

Michael Williams reviewed this cited source version on .

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-95: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. 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
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-36401 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
Critical
CVSS
9.8 (3.1)
Known Exploited
Yes
Published

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

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
0Timeline events
0ADP providers
8Source links

CISA KEV status

Status
Known exploited
Source
CISA / ADP
Date added
Not provided

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
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2024-36401Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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

Products and packages named in the record

VendorProductVersion / packageStatus
geoservergeoserver>= 2.23.0, < 2.23.6, >= 2.24.0, < 2.24.4, >= 2.25.0, < 2.25.2, < 2.22.6Listed
Weakness

CWE details

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

CWE-95 · source CWE mapping

Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection')

Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.