GHSA-68CF-J696-WVV9

Missing checks allow for SSRF to specific targets using the TestWfsPost enpoint.

Mitigation

To manage the proxy base value as a system administrator, use the parameter PROXY_BASE_URL to provide a non-empty value that cannot be overridden by the user interface or incoming request.thomsmith.

Resolution

The TestWfsPost has been replaced in GeoServer 2.25.2 and GeoServer 2.24.4 with a JavaScript Demo Requests page to test OGC Web Services.

References

• CVE-2024-29198 Unauthenticated SSRF via TestWfsPost

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.

GHSA-68CF-J696-WVV9 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 GHSA-68CF-J696-WVV9? GHSA-68CF-J696-WVV9 is a high-severity server-side request forgery (SSRF) vulnerability in org.geoserver:gs-wfs (maven), affecting versions >= 1.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 GHSA-68CF-J696-WVV9? GHSA-68CF-J696-WVV9 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 versions of org.geoserver:gs-wfs are affected by GHSA-68CF-J696-WVV9? org.geoserver:gs-wfs (maven) versions >= 1.0.0, < 2.24.4 is affected.
4. Is there a fix for GHSA-68CF-J696-WVV9? Yes. GHSA-68CF-J696-WVV9 is fixed in 2.24.4, 2.25.2. Upgrade to this version or later.
5. Is GHSA-68CF-J696-WVV9 exploitable, and should I be worried? Whether GHSA-68CF-J696-WVV9 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 GHSA-68CF-J696-WVV9 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 GHSA-68CF-J696-WVV9?
   • Upgrade org.geoserver:gs-wfs to 2.24.4 or later
   • Upgrade org.geoserver:gs-wfs to 2.25.2 or later