Skip to content

GHSA-jj54-8f66-c5pc CVE-2025-30220

[XBOW-025-068] XML External Entity (XXE) Processing Vulnerability in GeoServer WFS Service

Critical Maven
Severity
8.2 / 10
Critical · CVSS 3.1
Exploit chance (EPSS)
42.29%
Chance of exploitation in the next 30 days. Higher than 98.70% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-611 Improper Restriction of XML External Entity Reference
CWE-918 Server-Side Request Forgery (SSRF)
Fix
Available
2 packages have a fixed version

Description

Summary

GeoServer Web Feature Service (WFS) web service was found to be vulnerable to GeoTools CVE-2025-30220 XML External Entity (XXE) processing attack.

It is possible to trigger the parsing of external DTDs and entities, bypassing standard entity resolvers. This allows for Out-of-Band (OOB) data exfiltration of local files accessible by the GeoServer process, and Service Side Request Forgery (SSRF).

Details

While direct entity resolution is managed by application property ENTITY_RESOLUTION_ALLOWLIST for XML Parsing, this restriction was not being used by the GeoTools library when building an in-memory XSD Library Schema representation.

This bypasses GeoServer's AllowListEntityResolver enabling XXE attacks.

PoC

No public PoC is provided but this vulnerability has been confirmed to be exploitable through WFS service.

Impact

  • Information Disclosure:

    This vulnerability allows unauthenticated attackers to read arbitrary files from the server's filesystem that are accessible to the GeoServer process.

    This can lead to exposure of sensitive information including configuration files, credentials, and system files. The attack can be performed remotely without authentication, making it particularly severe.

  • Server-Side Request Forgery (SSRF)

    The mechanism inherently allows forcing GeoServer to make HTTP requests to arbitrary URLs, enabling SSRF attacks against internal network resources

References

Acknowledgements

This vulnerability was initially reported via an automated tool described below. Subsequently a duplicate report via @YacineF, and their patience working with the GeoServer project, was instrumental finding in escalating this issue and determining a resolution.

XBOW-025-068 Disclaimer

This vulnerability was detected using XBOW, a system that autonomously finds and exploits potential security vulnerabilities. The finding has been thoroughly reviewed and validated by a security researcher before submission. While XBOW is intended to work autonomously, during its development human experts ensure the accuracy and relevance of its reports.

Affected versions

Maven

PackageVulnerableFixed in
org.geoserver.web:gs-web-app
>= 2.27.0, < 2.27.1
2.27.1
org.geoserver.web:gs-web-app
>= 2.26.0, < 2.26.3
2.26.3
org.geoserver.web:gs-web-app
< 2.25.7
2.25.7
org.geoserver:gs-wfs
>= 2.27.0, < 2.27.1
2.27.1
org.geoserver:gs-wfs
>= 2.26.0, < 2.26.3
2.26.3
org.geoserver:gs-wfs
< 2.25.7
2.25.7

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

org.geoserver.web:gs-web-app Maven → 2.27.1

maven
<dependency><groupId>org.geoserver.web</groupId><artifactId>gs-web-app</artifactId><version>2.27.1</version></dependency>
gradle
implementation("org.geoserver.web:gs-web-app:2.27.1")

org.geoserver:gs-wfs Maven → 2.27.1

maven
<dependency><groupId>org.geoserver</groupId><artifactId>gs-wfs</artifactId><version>2.27.1</version></dependency>
gradle
implementation("org.geoserver:gs-wfs:2.27.1")

Severity breakdown

CVSS 3.1 8.2

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

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
Low

Weakness

CWE-611: Improper Restriction of XML External Entity Reference

The product processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output.

How to prevent it
  • Implementation, System Configuration: Many XML parsers and validators can be configured to disable external entity expansion.

CWE-918: Server-Side Request Forgery (SSRF)

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.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-fjf5-xgmq-5525
GeoServer is vulnerable to Unauthenticated XML External Entities (XXE) attack via WMS GetMap feature
Critical Known exploited Also affects org.geoserver.web:gs-web-app
GHSA-6jj6-gm7p-fcvv
Remote Code Execution (RCE) vulnerability in geoserver
Critical Known exploited Also affects org.geoserver:gs-wfs
GHSA-wf6j-gr27-g7ch
GeoServer has a Server-Side Template Injection (SSTI) vulnerability in processing FreeMarker templates
High Also affects org.geoserver.web:gs-web-app
GHSA-x4r9-gmw3-hxww
GeoServer has a Server-Side Request Forgery (SSRF) Vulnerability in its XML Entity Resolution
High Also affects org.geoserver.web:gs-web-app
GHSA-7qmg-grcp-qf25
GeoServer has an arbitrary file write vulnerability in its Master Password Dump Page
High Also affects org.geoserver.web:gs-web-app
GHSA-w66h-j855-qr72
GeoServer has a Reflected Cross-Site Scripting (XSS) vulnerability in its WMS GetFeatureInfo HTML format
Medium Also affects org.geoserver.web:gs-web-app
GHSA-gr67-pwcv-76gf
GeoServer Infinite Loop Vulnerability in Jiffle process
High Also affects org.geoserver.web:gs-web-app
GHSA-h86g-x8mm-78m5
GeoServer Missing Authorization on REST API Index
Medium Also affects org.geoserver.web:gs-web-app
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor