dbcve.org
GeoserverApplication · Osgeo

CVE-2024-29198

HIGH · 8.2 CVSS v3.1 Published 2025-06-10
Fix available
A fix is available. Upgrade to 2.24.4 / 2.25.2 or later.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

GeoServer contains a Service Side Request Forgery (SSRF) vulnerability in its Demo request endpoint. The vulnerability is exploitable when the Proxy Base URL configuration has not been set, allowing attackers to make the server perform requests to arbitrary URLs via the TestWfsPost servlet. The fix removes the TestWfsPost servlet entirely.

MitigationUpgrade to GeoServer 2.24.4 or 2.25.2, or ensure Proxy Base URL is properly configured in the server settings.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GeoserverApplication
Affected:>= 2.0.0, < 2.24.4>= 2.25.0, < 2.25.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed GeoServer version
    Access the GeoServer admin UI and navigate to About > Status, or check the warserver.txt or version file in the GeoServer data directory to find the exact version number
    Affected if The version is 2.0.0 through 2.24.3, or 2.25.0 through 2.25.1 (these fall within the vulnerable ranges)
  2. Verify Proxy Base URL configuration
    In GeoServer admin, go to Global settings and locate the Proxy Base URL field. Check whether a valid proxy URL is configured there
    Affected if Proxy Base URL is empty or not set - this is the condition that makes the server vulnerable
  3. Confirm TestWfsPost servlet presence
    Attempt to access the Demo request endpoint at /geoserver/web/demos/TestWfsPost (or check for the TestWfsPost servlet mapping in web.xml)
    Affected if The TestWfsPost servlet is present and accessible, indicating the vulnerable component has not been removed
  4. Check for recent security updates
    Review GeoServer change logs or release notes to confirm whether the instance has been updated after versions 2.24.4 or 2.25.2 were released
    Affected if The installation predates the 2.24.4 or 2.25.2 security releases and has not been patched

A user is affected if their GeoServer version is within the vulnerable range AND the Proxy Base URL is not configured, allowing the TestWfsPost servlet to be exploited for SSRF attacks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.24.4 / 2.25.2 or later
Fixed in 2.24.42.25.2
Interim mitigation

Upgrade to GeoServer 2.24.4 or 2.25.2, or ensure Proxy Base URL is properly configured in the server settings.

Recommended fix High confidence

GeoServer 2.24.4 or 2.25.2

  1. 1. Back up your current GeoServer installation, including data directory and any custom configurations
  2. 2. Download the fixed GeoServer version (2.24.4 or 2.25.2) from the official GeoServer distribution
  3. 3. Stop the running GeoServer service
  4. 4. Replace the existing GeoServer installation with the new version, preserving the data directory
  5. 5. Start the GeoServer service
  6. 6. Verify the TestWfsPost servlet has been removed by checking that the Demo request endpoint no longer accepts arbitrary URLs
  7. 7. Test that core GeoServer functionality (WMS, WFS, WCS services) continues to work correctly
Caveat The upgrade removes the TestWfsPost servlet which was accessible via the Demo endpoint - any workflows relying on this functionality will need to be updated

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Geoserver Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-29198 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-29198 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data