CVE-2024-40625

The Coverage rest api /workspaces/{workspaceName}/coveragestores/{storeName}/{method}.{format} allow to upload file with a specified url (with {method} equals 'url') with no restrict.

Details

The Coverage rest api /workspaces/{workspaceName}/coveragestores/{storeName}/{method}.{format} allow to upload file with a specified url (with {method} equals 'url'). But this url has not been check with URL Checks feature.

For example, should add the code below to check fileURL:

URLCheckers.confirm(fileURL)

The vulnerable code was RESTUtils.java

References

• https://osgeo-org.atlassian.net/browse/GEOS-11468
• https://osgeo-org.atlassian.net/browse/GEOS-11717

This vulnerability presents the opportunity for Server Side Request Forgery.

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-40625 has a CVSS score of 5.5 (Medium). The vector is network-reachable, high 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.26.0); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2024-40625? CVE-2024-40625 is a medium-severity server-side request forgery (SSRF) vulnerability in org.geoserver:gs-rest (maven), affecting versions < 2.26.0. It is fixed in 2.26.0. 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-40625? CVE-2024-40625 has a CVSS score of 5.5 (Medium). 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-40625?
   • org.geoserver:gs-rest (maven) (versions < 2.26.0)
   • org.geoserver.web:gs-web-app (maven) (versions < 2.26.0)
4. Is there a fix for CVE-2024-40625? Yes. CVE-2024-40625 is fixed in 2.26.0. Upgrade to this version or later.
5. Is CVE-2024-40625 exploitable, and should I be worried? Whether CVE-2024-40625 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-40625 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-40625?
   • Upgrade org.geoserver:gs-rest to 2.26.0 or later
   • Upgrade org.geoserver.web:gs-web-app to 2.26.0 or later