Classpath resource disclosure in GWC Web Resource API on Windows / Tomcat
CVE-2024-24749GHSA-jhqx-5v5g-mpf3
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (org.geoserver:gs-gwc 2.24.3, 2.23.5; org.geoserver.web:gs-web-app 2.24.3, 2.23.5), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Maven org.geoserver:gs-gwc
- Affected
- < 2.23.5>= 2.24.0, < 2.24.3
- Fixed in
- 2.24.3, 2.23.5
Maven org.geoserver.web:gs-web-app
- Affected
- < 2.23.5>= 2.24.0, < 2.24.3
- Fixed in
- 2.24.3, 2.23.5
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-jhqx-5v5g-mpf3 lists affected ranges: Maven org.geoserver.web:gs-web-app >=0 =2.24.0 =0 =2.24.0 <2.24.3
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- EPSS
- CVE-2024-24749: 0.76% estimated exploitation activity in the next 30 days; percentile 55.21 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
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).…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-jhqx-5v5g-mpf3
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2024-24749 Advisory: Classpath resource disclosure in GWC Web Resource API on Windows / Tomcat IDs: CVE-2024-24749, GHSA-jhqx-5v5g-mpf3 Record: https://patchnext.com/advisories/cve-2024-24749 (revision 1, source checked 26 Oct 2026, 16:40 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 7.5) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: org.geoserver:gs-gwc 2.24.3, 2.23.5; org.geoserver.web:gs-web-app 2.24.3, 2.23.5. A vendor fix does not mean a deployment is fixed. ## Affected components - Maven org.geoserver:gs-gwc: affected < 2.23.5; >= 2.24.0, < 2.24.3; fixed in 2.24.3, 2.23.5 - Maven org.geoserver.web:gs-web-app: affected < 2.23.5; >= 2.24.0, < 2.24.3; fixed in 2.24.3, 2.23.5 ## Suggested inspection (read-only) - Maven org.geoserver:gs-gwc: check the installed version with your package manager. - Maven org.geoserver.web:gs-web-app: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on org.geoserver:gs-gwc, org.geoserver.web:gs-web-app. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-jhqx-5v5g-mpf3 (GitHub-reviewed advisory GHSA-jhqx-5v5g-mpf3 lists affected ranges: Maven org.geoserver.web:gs-web-app >=0 =2.24.0 =0 =2.24.0 <2.24.3) Commands are suggestions: review each one before running it.
Loading voting…