CVE-2024-29198

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

• https://osgeo-org.atlassian.net/browse/GEOS-11794
• https://osgeo-org.atlassian.net/browse/GEOS-11390
• https://nvd.nist.gov/vuln/detail/CVE-2021-40822

Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside. Typical impact: access to internal metadata services, internal APIs, or cloud credentials.

CVE-2024-29198 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.24.4, 2.25.2); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2024-29198? CVE-2024-29198 is a high-severity server-side request forgery (SSRF) vulnerability in org.geoserver:gs-wfs (maven), affecting versions >= 2.0.0, < 2.24.4. It is fixed in 2.24.4, 2.25.2. Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside.
2. How severe is CVE-2024-29198? CVE-2024-29198 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2024-29198?
   • org.geoserver:gs-wfs (maven) (versions >= 2.0.0, < 2.24.4)
   • org.geoserver.web:gs-app (maven) (versions >= 2.0.0, < 2.24.4)
4. Is there a fix for CVE-2024-29198? Yes. CVE-2024-29198 is fixed in 2.24.4, 2.25.2. Upgrade to this version or later.
5. Is CVE-2024-29198 exploitable, and should I be worried? Whether CVE-2024-29198 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2024-29198 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2024-29198?
   • Upgrade org.geoserver:gs-wfs to 2.24.4 or later
   • Upgrade org.geoserver.web:gs-app to 2.24.4 or later
   • Upgrade org.geoserver:gs-wfs to 2.25.2 or later
   • Upgrade org.geoserver.web:gs-app to 2.25.2 or later