Skip to main content
ExploitedIn CISA KEVFix available

CVE-2024-36401

Exploitation confirmed. First attested on 2024-07-13 by CISA-ADP, CISA KEV, GCVE · kevintel, GCVE · shadowserver.

  • Published2024-07-01
  • Fixed in2.25.2 · 2.24.4 · 2.23.6 · 2.22.6
  • WeaknessCWE-94 · CWE-95

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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.

Timeline

dates in UTC
  1. 2024-07-0116:15CVE publishedNVD
  2. 2024-07-1303:55Exploitation first reportedCISA-ADP
  3. 2024-07-1303:55SSVC exploitation set to activeCISA-ADP
  4. 2024-07-15Added to the CISA KEV catalogCISA KEV
  5. 2024-07-15Listed as exploited by GCVEGCVE

Versions per branch

NVD · CISA-ADP · OSV
Geoserver
BranchAffectedFixed in
2.25≥ 2.25.0, < 2.25.22.25.2
2.24≥ 2.24.0, < 2.24.42.24.4
2.23≥ 2.23.0, < 2.23.62.23.6
2.23< 2.23.62.23.6
2.22< 2.22.62.22.6
Geotools
BranchAffectedFixed in
31.x≥ 31.1, < 31.231.2
30.x≥ 30.1, < 30.430.4
29.6< 29.629.6
30.0= 30.0no fix published
31.0= 31.0no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As GitHub_M, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • geoserver
    Affected
    • = >= 2.23.0, < 2.23.6no fix stated
    • = >= 2.24.0, < 2.24.4no fix stated
    • = >= 2.25.0, < 2.25.2no fix stated
    • = < 2.22.6no fix stated

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2025-03-19

Fix

  1. Update Geoserver to 2.25.2 · 2.24.4 · 2.23.6 · 2.22.6
  2. CISA’s required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.due 2024-08-05

Advisories and patches

Detection

read 2026-11-01 01:02 UTC
Nuclei template
available
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Metasploit modules
1 moduleexploit/multi/http/geoserver_unauth_rce_cve_2024_36401rank: excellentModule metadata: Metasploit Framework, © Rapid7, Inc., BSD-3-Clause.
Metasploit Framework

CISA Known Exploited Vulnerability

Date Added
2024-07-15
Patch Due Date
2024-08-05
Ransomware Use
Unknown
Required Action
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Published
2024-07-01
Last Modified
2026-06-17
NVD status
Analyzed
GitHub Advisory
GHSA-6jj6-gm7p-fcvv

Frequently asked questions

What is CVE-2024-36401?

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.

Is CVE-2024-36401 actively exploited?

Yes. CVE-2024-36401 is on the CISA Known Exploited Vulnerabilities (KEV) catalog, meaning it has been confirmed as actively exploited in the wild. CISA requires federal agencies to patch by 2024-08-05.

What is the CVSS score for CVE-2024-36401?

CVE-2024-36401 has a CVSS v3 base score of 9.8 (Critical severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record