GeoServer is an open source server that allows users to share and edit geospatial data. Prior to versions 2.23.5 and 2.24.3, 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). Versions 2.23.5 and 2.24.3 contain a patch for the issue. Some workarounds are available. One may change from a Windows environment to a Linux environment; or change from Apache Tomcat to Jetty application server. One may also disable anonymous access to the embeded GeoWebCache administration and status pages.

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

  - GeoServer is an open source server that allows users to share and edit geospatial data. Prior to versions
    2.23.5 and 2.24.3, 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). Versions 2.23.5 and
    2.24.3 contain a patch for the issue. Some workarounds are available. One may change from a Windows
    environment to a Linux environment; or change from Apache Tomcat to Jetty application server. One may also
    disable anonymous access to the embeded GeoWebCache administration and status pages. (CVE-2024-24749)

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.3. It is, therefore, affected by a Path Traversal.

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
416396	SCA: security update for org.geoserver.web:gs-web-app, org.geoserver:gs-gwc (GHSA-jhqx-5v5g-mpf3)	Tenable Cloud Security	SCA Checks	high
416396	SCA: security update for org.geoserver.web:gs-web-app, org.geoserver:gs-gwc (GHSA-jhqx-5v5g-mpf3)	Tenable Self-Hosted Container Security	SCA Checks	high
114532	GeoServer 2.24.0 < 2.24.3 Path Traversal	Web App Scanning	Component Vulnerability	high
114531	GeoServer < 2.23.5 Path Traversal	Web App Scanning	Component Vulnerability	high

Detections

Analytics

CVE-2024-24749

high

Tenable Plugins

high

high

high

high