Skip to main content

Geoserver CVE-2024-34711

| EUVDEUVD-2025-17669 CRITICAL
Information Exposure (CWE-200)
2025-06-10 security-advisories@github.com GHSA-mc43-4fqr-c965
9.3
CVSS 3.1 · GitHub Advisory
View

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK

2 techniques across 2 tactics: Collection, Discovery

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

Impact

This vulnerability presents a critical real-world risk based on multiple reinforcing signals: (1) CVSS 9.3 with AV:N/AC:L/PR:N indicates network-accessible exploitation requiring no authentication or user interaction—the most severe attack surface; (2) the vulnerability enables information disclosure with high confidence (C:H) and limited integrity impact (I:L), affecting CIA triad; (3) the nature of XXE vulnerabilities, combined with GeoServer's widespread use in geospatial infrastructure (government, utilities, environmental monitoring), suggests high organizational impact; (4) the bypass technique is deterministic and does not depend on exotic conditions, making exploitation highly automatable. While EPSS scoring is not provided in the CVE data, the combination of trivial exploitation (AC:L), no privilege requirement, and network accessibility strongly suggests EPSS well above 90th percentile. This is not a theoretical high-CVSS issue—it is a practical, immediately exploitable vulnerability suitable for widespread scanning and targeted attacks. Organizations should prioritize patching immediately. KEV status and POC availability have not been indicated in the provided data but should be verified against CISA KEV database and public exploit repositories given the vulnerability's severity and the time since disclosure.

Exploit ScenarioDerived

An unauthenticated attacker on the public internet targets an organization's GeoServer instance (AV:N). The attacker crafts a malicious XML document containing DOCTYPE declarations with XXE payloads designed to bypass the weak regex filter—for example, using a URI like 'http://internal-ip:8080/admin?file=config.xsd' or 'http://169.254.169.254/latest/meta-data' (AWS metadata) to extract sensitive information. The attacker submits this via GeoServer's WFS (Web Feature Service) GetPropertyValue request, POST upload, or style upload endpoints (AC:L, no authentication required). GeoServer's XML parser attempts to resolve the entity, bypassing the inadequate PreventLocalEntityResolver validation due to the regex flaw. The attacker receives the response containing internal system information (configuration files, credentials, internal IP ranges, AWS metadata), enabling reconnaissance of the internal network topology and systems. This intelligence is then leveraged for lateral movement, credential harvesting, or targeted exploitation of discovered internal services. The entire attack can be automated with standard XXE exploitation tools and executed at scale against multiple targets.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
Patch available 0.1% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Mar 14, 2026

CVE-2024-34711 is an improper URI validation vulnerability in GeoServer that allows unauthenticated attackers to bypass XML External Entity (XXE) filtering and perform information disclosure attacks against internal networks. The vulnerability affects GeoServer versions prior to 2.25.0, where a weak regex pattern in the PreventLocalEntityResolver class fails to adequately block malicious URIs, enabling attackers to make arbitrary HTTP requests and scan internal infrastructure. With a CVSS score of 9.3 and high exploitation probability, this vulnerability poses a significant risk for network reconnaissance and potential lateral movement attacks.

RemediationAI

Immediate patch: Upgrade GeoServer to version 2.25.0 or later, which defaults to ENTITY_RESOLUTION_ALLOWLIST and provides proper URI validation. For organizations unable to patch immediately: (1) Enable ENTITY_RESOLUTION_ALLOWLIST feature explicitly by setting system property org.geotools.xml.ENTITY_RESOLUTION_ALLOWLIST=true and configuring allowed external schemas; (2) Implement network-level controls restricting GeoServer's outbound HTTP/HTTPS connections to known, approved servers only; (3) Disable XXE processing at the XML parser level if not required by GeoServer features; (4) Restrict network access to GeoServer admin/REST API endpoints to trusted networks only; (5) Monitor GeoServer logs for suspicious XML entity resolution attempts and unexpected outbound connections. Vendor advisory and patch details should be obtained from GeoServer security advisory page (https://geoserver.org/announcements/vulnerability/) and the GeoTools project security advisories.

Affected VersionsENISA

geoserver < 2.25.0

Affected Packages

maven org.geoserver.main:gs-main fix: 2.25.0
maven org.geoserver.web:gs-web-app fix: 2.25.0
euvd geoserver fix: 2.25.0

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 3 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

GeoServer uses the PreventLocalEntityResolver class (from GeoTools library) to implement URI validation and filtering before resolving XML entities during document parsing. The vulnerability stems from a CWE-200 (Information Exposure) issue rooted in insufficient input validation. The current regex pattern (?i)(jar:file|http|vfs)[^?#;]*\.xsd is designed to allow only .xsd file extensions for specified protocols, but the negative character class [^?#;] fails to properly constrain the URI space. Attackers can exploit this by crafting URIs with query parameters, fragments, or other techniques to bypass the regex and reach arbitrary HTTP servers. The XXE attack vector leverages XML's DOCTYPE declarations to define external entities pointing to attacker-controlled or internal network resources. GeoServer versions 2.25.0 and later default to ENTITY_RESOLUTION_ALLOWLIST mode, which implements a positive allowlist approach rather than relying on blacklist-based regex filtering.

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 9.3 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/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
Changed
Confidentiality
High
Integrity
Low
Availability
None

Lifecycle Timeline

2
Patch released
Mar 31, 2026 - 21:13 nvd
Patch available
CVE Published
Jun 10, 2025 - 15:15 nvd
CRITICAL 9.3

DescriptionGitHub Advisory

GeoServer is an open source server that allows users to share and edit geospatial data. An improper URI validation vulnerability exists that enables an unauthorized attacker to perform XML External Entities (XEE) attack, then send GET request to any HTTP server. By default, GeoServer use PreventLocalEntityResolver class from GeoTools to filter out malicious URIs in XML entities before resolving them. The URI must match the regex (?i)(jar:file|http|vfs)[^?#;]*\\.xsd. But the regex leaves a chance for attackers to request to any HTTP server or limited file. Attacker can abuse this to scan internal networks and gain information about them then exploit further. GeoServer 2.25.0 and greater default to the use of ENTITY_RESOLUTION_ALLOWLIST and does not require you to provide a system property.

Executive ViewAI

Why It Matters

GeoServer instances are vulnerable to a critical XML External Entity (XXE) attack that allows attackers to bypass security filters and scan internal networks, potentially leading to data exfiltration or lateral movement. Organizations running GeoServer versions below 2.25.0 face immediate risk of network reconnaissance and further exploitation by external threat actors.

Business Impact: Severe
Compensating Controls

Since no patch is currently available for versions below 2.25.0, implement: (1) Web Application Firewall (WAF) rules to block XXE payloads in XML requests; (2) Network segmentation to restrict GeoServer's outbound HTTP connections to whitelisted internal hosts only; (3) Disable XML entity resolution features if not required for operations; (4) Monitor GeoServer logs for suspicious XML parsing attempts and unexpected outbound connections; (5) Apply the PreventLocalEntityResolver configuration manually with strict URI allowlists if available in your version. Expedite upgrade to 2.25.0+ as primary mitigation.

Threat Intelligence Overview

EPSS Score
0.1%
Top 71% exploitable
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 CRITICAL
CISA KEV No
Public POC No
EPSS 0.1%
Patch available Yes
Active threat No
Deciding rule
CRITICAL severity
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
None
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact
Very High

Priority Score

46
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +46
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

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