NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
HIGH severity

CVE-2024-29198 — gs-wfs

HIGH

CVE-2024-29198 is a high-severity (CVSS 7.5) Server-Side Request Forgery (SSRF) vulnerability in org.geoserver:gs-wfs. A fix is available for org.geoserver:gs-wfs — see the affected versions and patch details below.

GeoServer Vulnerable to Unauthenticated SSRF via TestWfsPost

Also known asGHSA-5gw5-jccf-6hxw
Published
Updated
Affected
4 pkgs
Patched
4 / 4
Exploits
None indexed
Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-29198.

EPSS Exploitation Probability

via FIRST.org ↗
2.3%probability of exploitation in next 30 days
Lower Risk+0.03%
Lower risk than most CVEs84th percentile — riskier than 84% of all scored CVEsHighest risk
0.00%4.20%8.39%12.6%10.1%2.3%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

4 pkgs affected
☕org.geoserver:gs-wfs☕org.geoserver.web:gs-app☕org.geoserver:gs-wfs☕org.geoserver.web:gs-app

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Summary

It possible to achieve Service Side Request Forgery (SSRF) via the Demo request endpoint if Proxy Base URL has not been set.

Details

A unauthenticated user can supply a request that will be issued by the server. This can be used to enumerate internal networks and also in the case of cloud instances can be used to obtain sensitive data.

Mitigation

  1. When using GeoServer with a proxy, manage the proxy base value as a system administrator, use the application property PROXY_BASE_URL to provide a non-empty value that cannot be overridden by the user interface or incoming request.

  2. When using GeoServer directly without a proxy, block all access to TestWfsPost by editing the web.xml file. Adding this block right before the end:

       <security-constraint>
        <web-resource-collection>
            <web-resource-name>BlockDemoRequests</web-resource-name>
            <url-pattern>/TestWfsPost/*</url-pattern>
        </web-resource-collection>
        <auth-constraint>
            <role-name>BLOCKED</role-name>
        </auth-constraint>
    </security-constraint>

Resolution

Upgrading to GeoServer 2.24.4, or 2.25.2, removes the TestWfsPost servlet resolving this issue.

The demo request page functionality is now implemented directly in the browser.

Reference

Affected Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.geoserver:gs-wfs≥ 2.0.0&&< 2.24.42.24.4org.geoserver:gs-wfs:2.24.4
☕Mavenorg.geoserver.web:gs-app≥ 2.0.0&&< 2.24.42.24.4org.geoserver.web:gs-app:2.24.4
☕Mavenorg.geoserver:gs-wfs≥ 2.25.0&&< 2.25.22.25.2org.geoserver:gs-wfs:2.25.2
☕Mavenorg.geoserver.web:gs-app≥ 2.25.0&&< 2.25.22.25.2org.geoserver.web:gs-app:2.25.2

Affected Products

1 product · 2 configurations
Application
geoserverosgeo
≥ 2.25.0 && < 2.25.2
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.geoserver:gs-wfs, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.geoserver:gs-wfs to 2.24.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-29198 is resolved across your whole dependency graph.

  3. Workarounds

    Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

How to detect CVE-2024-29198

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2024-29198 -u https://target
Template
GeoServer Demo Request Endpoint - Server Side Request Forgery
Severity
high
Impact
An attacker can exploit this vulnerability to access internal resources, enumerate internal networks, and potentially access sensitive data in cloud environments through the server-side request forgery attack.
Remediation
Upgrade to a patched version of GeoServer or configure the Proxy Base URL properly to prevent unauthorized server-side requests through the TestWfsPost endpoint.

Template by ProjectDiscovery nuclei-templates (iamnoooob, pdresearch), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

### Summary It possible to achieve Service Side Request Forgery (SSRF) via the Demo request endpoint if Proxy Base URL has not been set. ### Details A unauthenticated user can supply a request that will be issued by the server. This can be used to enumerate internal networks and also in the case of cloud instances can be used to obtain sensitive data. ### Mitigation 1. When using GeoServer with a proxy, manage the proxy base value as a system administrator, use the application property ``PROXY_BASE_URL`` to provide a non-empty value that cannot be overridden by the user interface or incom
O3 Security · Impact-Aware SCA

Is CVE-2024-29198 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2024-29198: gs-wfs SSRF — Fixed in 2.24.4