# CVE-2024-29198: GeoServer Vulnerable to Unauthenticated SSRF via TestWfsPost > Attackers can perform Server-Side Request Forgery via the TestWfsPost endpoint if Proxy Base URL is unset, potentially accessing internal resources. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 10 Jun 2025 - **Updated:** 17 Jun 2025 - **Also known as:** GHSA-5gw5-jccf-6hxw ## What is CVE-2024-29198? CVE-2024-29198 is a high-severity server-side request forgery vulnerability in geoserver, published on 10 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description GeoServer is an open source software server written in Java that allows users to share and edit geospatial data. It possible to achieve Service Side Request Forgery (SSRF) via the Demo request endpoint if Proxy Base URL has not been set. Upgrading to GeoServer 2.24.4, or 2.25.2, removes the TestWfsPost servlet resolving this issue. Weakness: CWE-918 (Server-Side Request Forgery) ## Which versions are affected by CVE-2024-29198? 8 open source packages ship an affected version, including org.geoserver.web:gs-app and org.geoserver:gs-wfs. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.geoserver.web:gs-app` | Maven | From 2.0.0 | 2.24.4 | | `org.geoserver.web:gs-app` | Maven | From 2.0.0 | 2.24.4 | | `org.geoserver.web:gs-app` | Maven | From 2.25.0 | 2.25.2 | | `org.geoserver.web:gs-app` | Maven | From 2.25.0 | 2.25.2 | | `org.geoserver:gs-wfs` | Maven | From 2.0.0 | 2.24.4 | | `org.geoserver:gs-wfs` | Maven | From 2.0.0 | 2.24.4 | | `org.geoserver:gs-wfs` | Maven | From 2.25.0 | 2.25.2 | | `org.geoserver:gs-wfs` | Maven | From 2.25.0 | 2.25.2 | Products: Osgeo Geoserver. ## How do I fix CVE-2024-29198? Upgrade org.geoserver.web:gs-app to a fixed version for your release line: 2.24.4 or 2.25.2. ## Is CVE-2024-29198 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-29198 exists. Public exploit code: - GeoServer Demo Request Endpoint - Server Side Request Forgery (nuclei): http/cves/2024/CVE-2024-29198.yaml ## Other vulnerabilities in geoserver - [CVE-2023-25157](https://insights.sbomify.com/CVE-2023-25157/): Unfiltered SQL Injection Vulnerabilities in Geoserver (critical 9.8) - [CVE-2024-34711](https://insights.sbomify.com/CVE-2024-34711/): GeoServer has improper ENTITY_RESOLUTION_ALLOWLIST URI validation in XML Processing (SSRF) (critical 9.3) - [CVE-2023-41339](https://insights.sbomify.com/CVE-2023-41339/): Unsecured WMS dynamic styling sld= parameter affords blind unauthenticated SSRF in GeoServer (high 8.6) - [CVE-2023-43795](https://insights.sbomify.com/CVE-2023-43795/): WPS Server Side Request Forgery in GeoServer (high 8.6) - [CVE-2025-30145](https://insights.sbomify.com/CVE-2025-30145/): GeoServer has an Infinite Loop Vulnerability in Jiffle process (high 7.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-29198 and fix it if it is affected. What it is: CVE-2024-29198 is a high-severity server-side request forgery vulnerability in geoserver, published on 10 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-29198 exists. Affected packages and fixed versions: - org.geoserver.web:gs-app (Maven): affected from 2.0.0; fixed in 2.24.4 - org.geoserver.web:gs-app (Maven): affected from 2.0.0; fixed in 2.24.4 - org.geoserver.web:gs-app (Maven): affected from 2.25.0; fixed in 2.25.2 - org.geoserver.web:gs-app (Maven): affected from 2.25.0; fixed in 2.25.2 - org.geoserver:gs-wfs (Maven): affected from 2.0.0; fixed in 2.24.4 - org.geoserver:gs-wfs (Maven): affected from 2.0.0; fixed in 2.24.4 - org.geoserver:gs-wfs (Maven): affected from 2.25.0; fixed in 2.25.2 - org.geoserver:gs-wfs (Maven): affected from 2.25.0; fixed in 2.25.2 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-29198/ (Markdown: https://insights.sbomify.com/CVE-2024-29198/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-29198 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-29198 - OSV: https://osv.dev/vulnerability/CVE-2024-29198 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-29198/ Summaries are generated and may contain mistakes; the official description above is the record.