Skip to content

GHSA-jm79-7xhw-6f6f CVE-2024-38524

GWC Home Page communicate version and revision information

High Maven
Severity
5.3 / 10
High · CVSS 3.1
Exploit chance (EPSS)
0.44%
Chance of exploitation in the next 30 days. Higher than 38.37% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
Fix
Available
2 packages have a fixed version

Description

Summary

The GeoWebCache home page includes version and revision information about the software in use. This information is sensitive from a security point of view because it allows software used by the server to be easily identified.

Details

org.geowebcache.GeoWebCacheDispatcher.handleFrontPage(HttpServletRequest, HttpServletResponse) has no check to hide potentially sensitive information from users except for a hidden system property to hide the storage locations that defaults to showing the locations.

PoC

Just open http://localhost:8080/geoserver/gwc/

Impact

In addition to exposing the version and revision information, the home page will expose the config file and storage locations which may expose the system's temp directory location and whether or not GeoServer is running in a Windows operating system. The approximate server start time and some basic GWC usage information is also exposed.

References

https://osgeo-org.atlassian.net/browse/GEOS-11677 https://github.com/geoserver/geoserver/pull/8189 https://github.com/GeoWebCache/geowebcache/issues/1344 https://github.com/GeoWebCache/geowebcache/pull/1345

Affected versions

Maven

PackageVulnerableFixed in
org.geoserver.web:gs-web-app
>= 2.26.0, < 2.26.2
2.26.2
org.geoserver.web:gs-web-app
< 2.25.6
2.25.6
org.geoserver:gs-gwc
>= 2.26.0, < 2.26.2
2.26.2
org.geoserver:gs-gwc
< 2.25.6
2.25.6

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

org.geoserver.web:gs-web-app Maven → 2.26.2

maven
<dependency><groupId>org.geoserver.web</groupId><artifactId>gs-web-app</artifactId><version>2.26.2</version></dependency>
gradle
implementation("org.geoserver.web:gs-web-app:2.26.2")

org.geoserver:gs-gwc Maven → 2.26.2

maven
<dependency><groupId>org.geoserver</groupId><artifactId>gs-gwc</artifactId><version>2.26.2</version></dependency>
gradle
implementation("org.geoserver:gs-gwc:2.26.2")

Severity breakdown

CVSS 3.1 5.3

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

Weakness

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

How to prevent it
  • Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-fjf5-xgmq-5525
GeoServer is vulnerable to Unauthenticated XML External Entities (XXE) attack via WMS GetMap feature
Critical Known exploited Also affects org.geoserver.web:gs-web-app
GHSA-6jj6-gm7p-fcvv
Remote Code Execution (RCE) vulnerability in geoserver
Critical Known exploited Also affects org.geoserver.web:gs-web-app
GHSA-wf6j-gr27-g7ch
GeoServer has a Server-Side Template Injection (SSTI) vulnerability in processing FreeMarker templates
High Also affects org.geoserver.web:gs-web-app
GHSA-x4r9-gmw3-hxww
GeoServer has a Server-Side Request Forgery (SSRF) Vulnerability in its XML Entity Resolution
High Also affects org.geoserver.web:gs-web-app
GHSA-7qmg-grcp-qf25
GeoServer has an arbitrary file write vulnerability in its Master Password Dump Page
High Also affects org.geoserver.web:gs-web-app
GHSA-w66h-j855-qr72
GeoServer has a Reflected Cross-Site Scripting (XSS) vulnerability in its WMS GetFeatureInfo HTML format
Medium Also affects org.geoserver.web:gs-web-app
GHSA-jj54-8f66-c5pc
[XBOW-025-068] XML External Entity (XXE) Processing Vulnerability in GeoServer WFS Service
Critical Also affects org.geoserver.web:gs-web-app
GHSA-gr67-pwcv-76gf
GeoServer Infinite Loop Vulnerability in Jiffle process
High Also affects org.geoserver.web:gs-web-app
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor