GeoServer is an open source software server written in Java that allows users to share and edit geospatial data. An arbitrary file renaming vulnerability exists in versions prior to 2.23.5 and 2.24.2 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. 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. Versions 2.23.5 and 2.24.2 contain a fix for this issue.

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - GeoServer is an open source software server written in Java that allows users to share and edit geospatial
    data. An arbitrary file renaming vulnerability exists in versions prior to 2.23.5 and 2.24.2 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. 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. Versions 2.23.5 and 2.24.2 contain a fix for this issue.
    (CVE-2024-23634)

According to its banner, the version of GeoServer running on the remote host is prior to 2.23.5 or 2.24.0 prior to 2.24.2. It is, therefore, affected by an Arbitrary File Renaming.

Note that the scanner has not tested for these issues but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Severity
411841	SCA: security update for org.geoserver:gs-restconfig (GHSA-75m5-hh4r-q9gx)	Tenable Cloud Security	SCA Checks	medium
411841	SCA: security update for org.geoserver:gs-restconfig (GHSA-75m5-hh4r-q9gx)	Tenable Self-Hosted Container Security	SCA Checks	medium
114533	GeoServer 2.24.0 < 2.24.2 Path Traversal	Web App Scanning	Component Vulnerability	medium

Detections

Analytics

CVE-2024-23634

medium

Tenable Plugins

medium

medium

medium