7.5
CWE
22 20
Advisory Published
Advisory Published
Updated

CVE-2024-24749: Classpath resource disclosure in GWC Web Resource API on Windows / Tomcat

First published: Mon Jul 01 2024(Updated: )

### Impact If GeoServer is deployed in the Windows operating system using an Apache Tomcat web application server, it is possible to bypass existing input validation in the GeoWebCache ByteStreamController class and read arbitrary classpath resources with specific file name extensions. If GeoServer is also deployed as a web archive using the data directory embedded in the geoserver.war file (rather than an external data directory), it will likely be possible to read specific resources to gain administrator privileges. However, it is very unlikely that production environments will be using the embedded data directory since, depending on how GeoServer is deployed, it will be erased and re-installed (which would also reset to the default password) either every time the server restarts or every time a new GeoServer WAR is installed and is therefore difficult to maintain. An external data directory will always be used if GeoServer is running in standalone mode (via an installer or a binary). ### Patches https://github.com/GeoWebCache/geowebcache/pull/1211 ### Workarounds Change environment: * Change from Windows operating system. This vulnerability depends on Windows file paths so Linux and Mac OS are not vulnerable. * Change from Apache Tomcat application server. Jetty and WildFly are confirmed to not be vulnerable. Other application servers have not been tested and may be vulnerable. Disable anonymous access to the embeded GeoWebCache administration and status pages: 1. Navigate to **Security > Authentication** Page 2. Locate **Filter Chains** heading 3. Select the ``web`` filter filter chain (ant pattern ``/web/**,/gwc/rest/web/**,/``) 4. Remove ``,/gwc/rest/web/**`` from the pattern (so that ``/web/**,/`` is left). 5. Save the changes ### References * CVE-Pending

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

Affected SoftwareAffected VersionHow to fix
maven/org.geoserver:gs-gwc>=2.24.0<2.24.3
2.24.3
maven/org.geoserver:gs-gwc<2.23.5
2.23.5
maven/org.geoserver.web:gs-web-app>=2.24.0<2.24.3
2.24.3
maven/org.geoserver.web:gs-web-app<2.23.5
2.23.5
All of
Any of
OSGeo GeoServer<2.23.5
OSGeo GeoServer>=2.24.0<2.24.3
Microsoft Windows Operating System

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-2024-24749?

    CVE-2024-24749 has a high severity due to the potential for input validation bypass and unauthorized access to sensitive classpath resources.

  • How do I fix CVE-2024-24749?

    To fix CVE-2024-24749, upgrade GeoServer to version 2.24.3 or 2.23.5, depending on the specific package in use.

  • Which versions of GeoServer are affected by CVE-2024-24749?

    CVE-2024-24749 affects GeoServer versions from 2.24.0 up to 2.24.3 and versions below 2.23.5.

  • What type of systems are impacted by CVE-2024-24749?

    CVE-2024-24749 impacts GeoServer deployments on Windows systems using the Apache Tomcat web application server.

  • Can CVE-2024-24749 lead to data leakage?

    Yes, CVE-2024-24749 can potentially lead to data leakage as it allows the reading of arbitrary classpath resources.

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