Skip to main content

Geoserver CVE-2024-29198

| EUVDEUVD-2024-26218 HIGH
Server-Side Request Forgery (SSRF) (CWE-918)
2025-06-10 security-advisories@github.com GHSA-5gw5-jccf-6hxw
7.5
CVSS 3.1 · GitHub Advisory
View

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V4 - API and Web Service URL allowlisting, SSRF prevention
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Credential Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Impact

This vulnerability presents genuine high risk despite the 7.5 CVSS score. The attack vector is Network with no authentication required (PR:N, UI:N), indicating broad exploitability. Attack complexity is Low, meaning exploitation does not require special conditions. The confidentiality impact is High (C:H) but integrity and availability are None, limiting direct data exfiltration but enabling reconnaissance and lateral movement attacks. The SSRF vector is particularly dangerous in cloud environments where SSRF can access metadata services (AWS IMDSv1, GCP metadata) to extract credentials. While the CVSS score suggests moderate impact, real-world risk is elevated because: (1) SSRF enables stepping-stone attacks into internal networks, (2) GeoServer often runs in geospatial/critical infrastructure contexts, (3) the vulnerability is pre-authentication, and (4) the presence of specific patched versions (2.24.4, 2.25.2) suggests active exploitation awareness. Organizations using unpatched versions with public-facing GeoServer instances face immediate compromise risk.

Exploit ScenarioDerived

An attacker discovers a public-facing GeoServer instance without Proxy Base URL configured. The attacker crafts a malicious HTTP request to the Demo endpoint (e.g., GET /geoserver/web/wicket/resource/demo?url=http://169.254.169.254/latest/meta-data/) targeting AWS EC2 instance metadata. The GeoServer server processes this request and makes an outbound HTTP connection to the internal metadata service, returning sensitive information (IAM credentials, instance details) in the response. The attacker captures this response, extracts AWS credentials with attached IAM policies, and uses them for lateral movement into the organization's AWS environment. Alternatively, the attacker targets internal services (e.g., http://internal-database:5432) to probe for open ports and services, gathering intelligence for further attacks. No special PoC is required; standard HTTP clients and simple URL manipulation suffice due to the Low attack complexity and pre-authentication nature of the vulnerability.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 6.4% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 14, 2026

GeoServer contains a Server-Side Request Forgery (SSRF) vulnerability in the Demo request endpoint (TestWfsPost servlet) that allows unauthenticated network attackers to make arbitrary HTTP requests from the server when Proxy Base URL is not configured. This high-severity vulnerability (CVSS 7.5) affects GeoServer versions prior to 2.24.4 and 2.25.2, enabling attackers to access internal resources, cloud metadata endpoints, and potentially interact with backend systems.

RemediationAI

Immediate remediation: (1) Upgrade to GeoServer 2.24.4 or later, or upgrade to GeoServer 2.25.2 or later, which removes the vulnerable TestWfsPost servlet entirely. (2) If immediate patching is not feasible, apply network-level mitigations: restrict network access to GeoServer's demo endpoints using firewall rules, WAF rules, or reverse proxy configurations to block requests to /geoserver/web/wicket/resource/demo paths. (3) Implement strict URL validation: configure 'Proxy Base URL' in GeoServer settings (Settings > Global > Proxy Base URL) to enforce a whitelist of allowed proxy destinations. (4) Disable the demo request functionality if not required by setting appropriate security constraints in web.xml or disabling the TestWfsPost servlet registration. (5) Monitor access logs for suspicious requests to demo endpoints with unusual URL parameters. Vendor advisory and patches available at GeoServer GitHub security releases and official security bulletins.

Affected VersionsENISA

geoserver 2.25.0, < 2.25.2
geoserver 2.0.0, < 2.24.4

Affected Packages

maven org.geoserver.web:gs-app fix: 2.24.4, 2.25.2
maven org.geoserver:gs-wfs fix: 2.24.4, 2.25.2
euvd geoserver_2_0_0 fix: 2.24.4
euvd geoserver_2_25_0 fix: 2.25.2

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 4 packages in maven, euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerability exists in GeoServer's TestWfsPost servlet, a demonstration endpoint used for testing Web Feature Service (WFS) POST requests. The root cause is CWE-918 (Server-Side Request Forgery), which occurs because user-supplied input to the Demo endpoint is not properly validated before being used to construct HTTP requests. When Proxy Base URL configuration is absent, the application fails to enforce proper URL validation and filtering, allowing attackers to specify arbitrary destination URLs. The servlet processes these requests server-side without adequate sanitization, enabling SSRF attacks. GeoServer is written in Java and runs on application servers like Tomcat, making it a network-accessible target when exposed to untrusted networks.

Know when Geoserver gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

GitHub Advisory PRIMARY 7.5 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

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

Lifecycle Timeline

3
Patch released
Mar 31, 2026 - 21:13 nvd
Patch available
PoC Detected
Aug 26, 2025 - 16:25 vuln.today
Public exploit code
CVE Published
Jun 10, 2025 - 15:15 nvd
HIGH 7.5

DescriptionGitHub Advisory

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.

Executive ViewAI

Why It Matters

GeoServer instances without a configured Proxy Base URL are vulnerable to Server-Side Request Forgery (SSRF) attacks, potentially allowing threat actors to access internal resources and sensitive data. Organizations running affected GeoServer versions face immediate risk if the Demo request endpoint is exposed or accessible to untrusted users.

Business Impact: High
Compensating Controls
  1. Configure Proxy Base URL in GeoServer settings to mitigate SSRF vector. 2) Disable or restrict access to the Demo request endpoint and TestWfsPost servlet via firewall/WAF rules. 3) Implement network segmentation to limit GeoServer's ability to reach internal systems. 4) Monitor outbound connections from GeoServer for unauthorized internal resource access. 5) Restrict GeoServer access to authenticated users only. Monitor vendor advisories for patch availability and apply immediately upon release.

Threat Intelligence Overview

EPSS Score
6.4%
Top 9% exploitable
Exploit
POC
Public exploit code exists
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC Yes
EPSS 6.4%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Out-of-Cycle
Exploitation· derived
Poc
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact
High

Priority Score

64
Low Medium High Critical
KEV: 0
EPSS: +6
CVSS: +38
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Server-Side Request Forgery exploits applications that fetch remote resources based on user-supplied URLs.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy