EUVD-2025-210278
GHSA-x4r9-gmw3-hxww
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L
Network-reachable unauthenticated SSRF, but exploitation requires a specific path-less proxy base URL configuration so AC:H; impact is information disclosure via SSRF (C:H, I:N, A:N).
Primary rating from NVD.
CVSS VectorNVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L
Lifecycle Timeline
7DescriptionNVD
Summary
A GeoServer that uses ENTITY_RESOLUTION_ALLOWLIST may allow attacker to perform unauthenticated Server-Side Request Forgery (SSRF).
Details
This vulnerability requires that GeoServer is set up to use a proxy base URL and the ENTITY_RESOLUTION_ALLOWLIST (default since 2.25.0):
Impact
This vulnerability allows an attacker to cause GeoServer to make requests to an unintended location.
Workaround
GeoServer installations are only affected by this vulnerability if they use a proxy base URL that does not contain a URL path or end with a slash (e.g., https://somesite.org instead of https://somesite.org/ or https://somesite.org/geoserver). If the proxy base URL does not contain a path, adding a slash to the end of the URL will mitigate this vulnerability.
Resources
https://osgeo-org.atlassian.net/browse/GEOS-11867 https://github.com/geoserver/geoserver/pull/8622
Credits:
- Le Mau Anh Phong at Verichains Cyber Force
AnalysisAI
Server-Side Request Forgery in GeoServer 2.26.x prior to 2.26.4 and 2.27.x prior to 2.27.3 allows unauthenticated remote attackers to coerce the server into issuing HTTP requests to attacker-chosen destinations by abusing weak prefix matching of the proxy base URL inside the XML entity resolver. No public exploit identified at time of analysis, and EPSS exploitation probability sits at 0.06% (19th percentile), but the trivial network-only attack vector and default-enabled ENTITY_RESOLUTION_ALLOWLIST since 2.25.0 raise the realistic exposure for internet-facing instances.
Technical ContextAI
GeoServer is an open-source Java web application (built on GeoTools and packaged as the gs-main and gs-web-app Maven artifacts) that publishes geospatial data through OGC services such as WMS, WFS and WCS. XML payloads processed by these services can declare external entities, and GeoServer mitigates XXE through the AllowListEntityResolver, which permits only URIs starting with the configured proxy base URL, internal data-directory schemas, or specific built-in locations. The CWE-20 (improper input validation) root cause is in that allowlist check: when the configured proxy base URL has no path component and no trailing slash (e.g. https://somesite.org), a case-insensitive startsWith comparison treats any URL that begins with that hostname prefix - including unrelated hosts such as https://somesite.org.attacker.tld - as trusted, letting an attacker steer XML entity resolution to an arbitrary host. The pull/8622 patch replaces the raw startsWith check with a urlStartsWith helper and adds URI normalisation, escape-sequence filtering and an explicit ENTITY_RESOLUTION_UNRESTRICTED_INTERNAL property.
RemediationAI
Vendor-released patch: upgrade to GeoServer 2.26.4 or 2.27.3 (or any later release), which apply the AllowListEntityResolver fix from pull request https://github.com/geoserver/geoserver/pull/8622 and add the new ENTITY_RESOLUTION_UNRESTRICTED_INTERNAL safety toggle. If immediate upgrade is not possible, the vendor-documented workaround is to append a trailing slash to the configured proxy base URL (e.g. change https://somesite.org to https://somesite.org/ or https://somesite.org/geoserver), which forces the allowlist prefix check to match only the intended origin; this change is low-risk but should be validated against any downstream clients or reverse-proxy rewrites that assume the prior URL form. As an additional compensating control, restrict GeoServer's egress at the network layer to deny outbound traffic to cloud metadata IPs (e.g. 169.254.169.254), RFC1918 ranges and other internal services, accepting that this may also break legitimate outbound XSD or schema fetches and should be tested against your service catalogue. Refer to https://github.com/geoserver/geoserver/security/advisories/GHSA-x4r9-gmw3-hxww for the canonical advisory.
Atlassian has been made aware of an issue reported by a handful of customers where external attackers may have exploited
The HipChat for JIRA plugin before 6.30.0 for Atlassian JIRA allows remote authenticated users to execute arbitrary Java
Atlassian Confluence before 5.8.17 allows remote authenticated users to read configuration files via the decoratorName p
Atlassian JIRA before 5.0.1; Confluence before 3.5.16, 4.0 before 4.0.7, and 4.1 before 4.1.10; FishEye and Crucible bef
Directory traversal vulnerability in the Issue Collector plugin in Atlassian JIRA before 6.0.4 allows remote attackers t
All versions of Confluence Data Center and Server are affected by this unexploited vulnerability. Rated critical severit
In affected versions of Confluence Server and Data Center, an OGNL injection vulnerability exists that would allow an un
Atlassian Crowd and Crowd Data Center had the pdkinstall development plugin incorrectly enabled in release builds. Rated
The IconUriServlet of the Atlassian OAuth Plugin from version 1.3.0 before version 1.9.12 and from version 2.0.0 before
This High severity RCE (Remote Code Execution) vulnerability was introduced in version 5.2 of Confluence Data Center and
Multiple API endpoints in Atlassian Bitbucket Server and Data Center 7.0.0 before version 7.6.17, from version 7.7.0 bef
The JIRA Workflow Designer Plugin in Atlassian JIRA Server before 6.3.0 improperly uses an XML parser and deserializer,
Same weakness CWE-20 – Improper Input Validation
View allShare
External POC / Exploit Code
Leaving vuln.today