cve.bz

CVE-2024-29198 osgeo geoserver: SSRF

8.2 highEPSS 2.3%Fix available

High (8.2) in osgeo geoserver. EPSS 2.3% estimated probability of exploitation activity in the next 30 days. Fixed in org.geoserver:gs-wfs 2.24.4, 2.25.2.

On this page
GeoServer is an open source software server written in Java that allows users to share and edit geospatial data. It possible to achieve Service Side Request Forgery (SSRF) via the Demo request endpoint if Proxy Base URL has not been set. Upgrading to GeoServer 2.24.4, or 2.25.2, removes the TestWfsPost servlet resolving this issue.

Severity

CVSS 3.1

8.2 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
EPSS
2.3% (unchanged from 2.3% a week ago; 2.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 84th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2025-06-10. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-918 Server-Side Request Forgery (SSRF)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

  • org.geoserver:gs-wfs (Maven): fixed in 2.24.4, 2.25.2
  • org.geoserver.web:gs-app (Maven): fixed in 2.24.4, 2.25.2

Ask an AI about this CVE

Show the promptExplain CVE-2024-29198 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2024-29198?via=ask-ai-copy and https://cve.bz/cve/CVE-2024-29198?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2024-29198 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
osgeo:geoserverfrom 2.0.0 before 2.24.4
osgeo:geoserverfrom 2.25.0 before 2.25.2

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-5gw5-jccf-6hxwMavenorg.geoserver:gs-wfs>=2.0.0 <2.24.42.24.4
GHSA-5gw5-jccf-6hxwMavenorg.geoserver.web:gs-app>=2.0.0 <2.24.42.24.4
GHSA-5gw5-jccf-6hxwMavenorg.geoserver:gs-wfs>=2.25.0 <2.25.22.25.2
GHSA-5gw5-jccf-6hxwMavenorg.geoserver.web:gs-app>=2.25.0 <2.25.22.25.2

Detection rules

Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.

Attack patterns (CAPEC)

  • CAPEC-664 Server Side Request Forgery Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON