Log in Start free

Vulnerability · Published Mar 20, 2024 · Assigned by GitHub_M

CVE-2024-23634GeoServer arbitrary file renaming vulnerability in REST Coverage/Data Store API

Medium 6.0

In plain English

A medium-severity improper input validation in geoserver from geoserver. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.7% (higher than 53% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)6.0Medium
Exploit odds (30 days)0.7%top 46.9% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official description

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.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Mavenorg.geoserver:gs-restconfig2.23.5GHSA-75m5-hh4r-q9gx
Mavenorg.geoserver:gs-restconfig2.24.2GHSA-75m5-hh4r-q9gx

Affected products (as reported)

VendorProductVersions
geoserver geoserver < 2.23.5>= 2.24.0, < 2.24.2

Weakness: CWE-20, CWE-73 · Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:H

References