Advisory record · GHSA-j59v-vgcr-hxvf

GeoServer's Server Status shows sensitive environmental variables and Java properties

CVSS 4.5 MediumEPSS 0.0040 · 34th percentile

Published by the GitHub Advisory Database at 1 Jul 2024, 19:20 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.geoserver.web:gs-web-appMaven>=2.10.0, <2.24.4 || >=2.25.0, <2.25.12.24.4, 2.25.1
org.geoserver:gs-mainMaven>=2.10.0, <2.24.4 || >=2.25.0, <2.25.12.24.4, 2.25.1
Identifiers
GHSA-j59v-vgcr-hxvf · CVE-2024-34696
Weakness (CWE)
CWE-200
Published
1 Jul 2024
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

GeoServer versions from 2.10.0 up to 2.24.4 and from 2.25.0 up to 2.25.1 (packages org.geoserver.web:gs-web-app and org.geoserver:gs-main) show all environment variables and Java properties on the Server Status page and in the about status REST endpoint to any user with administrator rights. An administrator can then see secrets such as database passwords or API keys that these values may contain. Upgrade to GeoServer 2.24.4 or 2.25.1, which hide these values by default. Avoid enabling the setting that re-displays them, and keep secrets out of environment variables where possible.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
4.5 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:N/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0040, the 34th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:17 UTC First seen by agentprime
  2. 31 Oct 2026, 14:17 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.