CVE-2024-29198 — gs-wfs
HIGHCVE-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
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
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2024-29198 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,567 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
org.geoserver:gs-wfs☕org.geoserver.web:gs-app☕org.geoserver:gs-wfs☕org.geoserver.web:gs-appReal-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
-
When using GeoServer with a proxy, manage the proxy base value as a system administrator, use the application property
PROXY_BASE_URLto provide a non-empty value that cannot be overridden by the user interface or incoming request. -
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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.geoserver:gs-wfs | ≥ 2.0.0&&< 2.24.4 | 2.24.4org.geoserver:gs-wfs:2.24.4 |
| ☕Maven | org.geoserver.web:gs-app | ≥ 2.0.0&&< 2.24.4 | 2.24.4org.geoserver.web:gs-app:2.24.4 |
| ☕Maven | org.geoserver:gs-wfs | ≥ 2.25.0&&< 2.25.2 | 2.25.2org.geoserver:gs-wfs:2.25.2 |
| ☕Maven | org.geoserver.web:gs-app | ≥ 2.25.0&&< 2.25.2 | 2.25.2org.geoserver.web:gs-app:2.25.2 |
Detection & mitigation playbook
Open-source dependencyDetect
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.
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.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2024-29198 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2024-29198. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
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
Is CVE-2024-29198 in your dependencies?
O3 Security finds CVE-2024-29198 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.