CVE-2024-40625 Details
Description
GeoServer is an open source server that allows users to share and edit geospatial data. The Coverage rest api /workspaces/{workspaceName}/coveragestores/{storeName}/{method}.{format} allows attackers to upload files with a specified url (with {method} equals 'url') with no restrict. This vulnerability is fixed in 2.26.0.
A server-side request forgery (SSRF) vulnerability has been identified in GeoServer versions prior to 2.26.0. The issue arises in the Coverage REST API, specifically within the endpoint that allows file uploads from a specified URL. This functionality, available through the 'url' method, lacks proper validation, enabling potential exploitation by uploading malicious files from unverified sources.
Users can upgrade to GeoServer version 2.26.0 or later to address this vulnerability.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Jun 10, 2025References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://github.com/geoserver/geoserver/security/advisories/GHSA-r4hf-r8gj-jgw2 | [email protected] | Third Party Advisory |
| https://osgeo-org.atlassian.net/browse/GEOS-11468 | [email protected] | Issue TrackingPatch |
| https://osgeo-org.atlassian.net/browse/GEOS-11717 | [email protected] | Permissions Required |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-918 | Server-Side Request Forgery (SSRF) | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| osgeo geoserver | < 2.26.0 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Aug 26, 2025 | Initial Analysis | [email protected] |
| Jun 10, 2025 | New CVE Received | [email protected] |