CVE-2024-34696: GeoServer's Server Status shows sensitive environmental variables and Java properties
First published: Mon Jul 01 2024(Updated: )
GeoServer is an open source server that allows users to share and edit geospatial data. Starting in version 2.10.0 and prior to versions 2.24.4 and 2.25.1, GeoServer's Server Status page and REST API lists all environment variables and Java properties to any GeoServer user with administrative rights as part of those modules' status message. These variables/properties can also contain sensitive information, such as database passwords or API keys/tokens. Additionally, many community-developed GeoServer container images `export` other credentials from their start-up scripts as environment variables to the GeoServer (`java`) process. The precise scope of the issue depends on which container image is used and how it is configured. The `about status` API endpoint which powers the Server Status page is only available to administrators.Depending on the operating environment, administrators might have legitimate access to credentials in other ways, but this issue defeats more sophisticated controls (like break-glass access to secrets or role accounts).By default, GeoServer only allows same-origin authenticated API access. This limits the scope for a third-party attacker to use an administrator’s credentials to gain access to credentials. The researchers who found the vulnerability were unable to determine any other conditions under which the GeoServer REST API may be available more broadly. Users should update container images to use GeoServer 2.24.4 or 2.25.1 to get the bug fix. As a workaround, leave environment variables and Java system properties hidden by default. Those who provide the option to re-enable it should communicate the impact and risks so that users can make an informed choice.
Credit: security-advisories@github.com security-advisories@github.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| maven/org.geoserver:gs-main | >=2.25.0<2.25.1 | 2.25.1 |
| maven/org.geoserver:gs-main | >=2.10.0<2.24.4 | 2.24.4 |
| maven/org.geoserver.web:gs-web-app | >=2.25.0<2.25.1 | 2.25.1 |
| maven/org.geoserver.web:gs-web-app | >=2.10.0<2.24.4 | 2.24.4 |
| OSGeo GeoServer | >=2.10.0<2.24.4 | |
| OSGeo GeoServer | >=2.25.0<2.25.1 |
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.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2024-34696?
CVE-2024-34696 has been classified with a severity rating that indicates a potential exposure of sensitive data due to the disclosure of environment variables and Java properties.
How do I fix CVE-2024-34696?
To resolve CVE-2024-34696, update GeoServer to version 2.24.4 or 2.25.1 or later.
Which versions of GeoServer are affected by CVE-2024-34696?
CVE-2024-34696 affects GeoServer versions from 2.10.0 up to but not including 2.24.4 and 2.25.1.
What impact does CVE-2024-34696 have on GeoServer installations?
The impact of CVE-2024-34696 allows unauthorized users to access environment variables and Java properties, potentially leading to sensitive information exposure.
Is there a workaround for CVE-2024-34696?
There is no specific workaround for CVE-2024-34696; the only way to mitigate risk is to upgrade to the patched versions.
- agent/title
- agent/type
- agent/first-publish-date
- collector/github-advisory-latest
- source/GitHub
- alias/GHSA-j59v-vgcr-hxvf
- alias/CVE-2024-34696
- agent/software-canonical-lookup
- agent/weakness
- agent/references
- agent/description
- agent/severity
- agent/event
- agent/author
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/trending
- agent/source
- agent/softwarecombine
- agent/tags
- collector/nvd-cve
- source/NVD
- agent/software-canonical-lookup-request
- collector/nvd-api
- package-manager/maven
- vendor/geoserver
- canonical/osgeo geoserver
- version/osgeo geoserver/2.10.0
- version/osgeo geoserver/2.25.0