CVE-2024-29198VulnerabilityPublished 10 Jun 2025

CVE-2024-29198: geoserver · Server-Side Request Forgery (SSRF)

Affects geoserverSource CVE Database V5

Not known to be exploited · public detection template (Nuclei) · CVSS 7.5 High : upgrade to 2.25.2 or 2.24.4 soon.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 2.2% chance of exploitation in 30 days – higher than 83% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2.25.2, 2.24.4

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Jun 2025
Detectable: evidence found.
nuclei template: GeoServer Demo Request Endpoint - Server Side Request Forgery
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade org.geoserver/geoserver to 2.25.2 or 2.24.4.

Affected software

Product	Affected	Fixed in
Mavenorg.geoserver/geoserver`pkg:maven/org.geoserver/geoserver`Other threats	Affected <2.24.4 <2.25.2	Fixed in 2.24.4 2.25.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate this vulnerability, European organizations should immediately upgrade affected GeoServer instances to versions 2.24.4 or 2.25.2 or later, which remove the vulnerable TestWfsPost servlet. If upgrading is not immediately feasible, organizations should disable or restrict access to the Demo request endpoint and the TestWfsPost servlet to trusted internal networks only. Additionally, setting the Proxy Base URL configuration properly can prevent SSRF exploitation by restricting the URLs GeoServer can access internally. Network-level controls such as firewall rules should be implemented to limit outbound HTTP requests from the GeoServer host to only necessary destinations. Monitoring and logging HTTP requests originating from GeoServer can help detect suspicious activity. Finally, organizations should review their internal network segmentation and access controls to minimize the impact of any potential SSRF exploitation.

Description

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.

Impact

For European organizations, the impact of this SSRF vulnerability in GeoServer can be significant, especially for entities relying on geospatial data services such as government agencies, urban planning departments, environmental monitoring organizations, and private companies in sectors like transportation, utilities, and telecommunications. Exploiting this vulnerability could allow attackers to access sensitive internal network resources, potentially exposing confidential geospatial data or other internal services. This could lead to unauthorized data disclosure, reconnaissance for further attacks, or pivoting deeper into the network. Since GeoServer is often deployed in environments with sensitive or critical infrastructure data, the confidentiality breach could have regulatory and operational consequences. Additionally, the lack of required authentication and user interaction increases the risk of automated exploitation attempts. Although no active exploits are known yet, the widespread use of GeoServer in Europe and the high severity score suggest that organizations should prioritize remediation to avoid potential future attacks.

Summary

CVE-2024-29198 is a high-severity Server-Side Request Forgery (SSRF) vulnerability affecting GeoServer, an open-source Java-based server used for sharing and editing geospatial data. The vulnerability exists in the Demo request endpoint when the Proxy Base URL configuration is not set. An attacker can exploit this flaw to make the GeoServer instance send crafted HTTP requests to internal or external systems on behalf of the server, potentially accessing internal resources that are otherwise inaccessible from the outside. This SSRF vulnerability arises from improper validation and control of URLs that the server requests internally. The affected versions include GeoServer releases from 2.0.0 up to but not including 2.24.4, and from 2.25.0 up to but not including 2.25.2. The issue is resolved by upgrading to GeoServer 2.24.4 or 2.25.2, which remove the vulnerable TestWfsPost servlet responsible for this behavior. The CVSS v3.1 base score is 7.5, reflecting the network attack vector, low attack complexity, no privileges or user interaction required, and a high impact on confidentiality but no impact on integrity or availability. No known exploits are currently reported in the wild. This vulnerability is classified under CWE-918, which covers SSRF issues where an attacker can abuse server functionality to induce the server to make HTTP requests to arbitrary domains, including internal networks.

CWE-918Server-Side Request Forgery (SSRF) (opens in a new tab)
Base weaknessCWE Top 25 (2025): #22OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.6.1 (opens in a new tab)
V5.2.6 (opens in a new tab)
Attack patterns
Server Side Request Forgery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Jul 2025, 03:20 UTC

Public exploits and detectiona Nuclei detection template

WeaknessesCWE-918

Technical details

References

Community reviews

Related threats