6 Medium
CVSS3
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
HIGH
User Interaction
NONE
Scope
UNCHANGED
Confidentiality Impact
LOW
Integrity Impact
LOW
Availability Impact
HIGH
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:H
7.2 High
AI Score
Confidence
High
0.0004 Low
EPSS
Percentile
15.7%
An arbitrary file renaming vulnerability exists that enables an authenticated administrator with permissions to modify stores through the REST Coverage Store or Data Store API to rename arbitrary files and directories with a name that does not end in “.zip”.
Store file uploads rename zip files to have a “.zip” extension if it doesn’t already have one before unzipping the file. This is fine for file and url upload methods where the files will be in a specific subdirectory of the data directory but, when using the external upload method, this allows arbitrary files and directories to be renamed.
Coverage Store Example (workspace and store name are irrelevant and any valid coverage format can be used):
curl -XPUT -H"Content-Type:application/zip" -u"admin:geoserver" -d"/file/to/move" “http://localhost:8080/geoserver/rest/workspaces/a/coveragestores/b/external.geotiff”
Data Store Example (workspace and store name and data store format are irrelevant):
curl -XPUT -H"Content-Type:application/zip" -u"admin:geoserver" -d"/file/to/move" “http://localhost:8080/geoserver/rest/workspaces/a/datastores/b/external.c”
Renaming GeoServer files will most likely result in a denial of service, either completely preventing GeoServer from running or effectively deleting specific resources (such as a workspace, layer or style). In some cases, renaming GeoServer files could revert to the default settings for that file which could be relatively harmless like removing contact information or have more serious consequences like allowing users to make OGC requests that the customized settings would have prevented them from making. The impact of renaming non-GeoServer files depends on the specific environment although some sort of denial of service is a likely outcome.
https://osgeo-org.atlassian.net/browse/GEOS-11213
https://github.com/geoserver/geoserver/pull/7289
CPE | Name | Operator | Version |
---|---|---|---|
org.geoserver:gs-restconfig | lt | 2.24.2 | |
org.geoserver:gs-restconfig | lt | 2.23.5 |
github.com/advisories/GHSA-75m5-hh4r-q9gx
github.com/geoserver/geoserver/commit/5d6af2f8ba9ad7dffae59575504a867159698772
github.com/geoserver/geoserver/commit/c37f58fbacdfa0d581a6f99195585f70b1201f0a
github.com/geoserver/geoserver/pull/7289
github.com/geoserver/geoserver/security/advisories/GHSA-75m5-hh4r-q9gx
nvd.nist.gov/vuln/detail/CVE-2024-23634
osgeo-org.atlassian.net/browse/GEOS-11213
6 Medium
CVSS3
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
HIGH
User Interaction
NONE
Scope
UNCHANGED
Confidentiality Impact
LOW
Integrity Impact
LOW
Availability Impact
HIGH
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:H
7.2 High
AI Score
Confidence
High
0.0004 Low
EPSS
Percentile
15.7%