Classpath resource disclosure in GWC Web Resource API on Windows / Tomcat
ImpactIf 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).Patcheshttps://github.com/GeoWebCache/geowebcache/pull/1211WorkaroundsChange 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:Navigate to **Security > Authentication** PageLocate **Filter Chains** headingSelect the ``web`` filter filter chain (ant pattern ``/web/**,/gwc/rest/web/**,/``)Remove ``,/gwc/rest/web/**`` from the pattern (so that ``/web/**,/`` is left).Save the changesReferencesCVE-Pending