How severe is GHSA-mc43-4fqr-c965?

GHSA-mc43-4fqr-c965 has a CVSS score of 9.3/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-mc43-4fqr-c965?

GHSA-mc43-4fqr-c965 affects the following packages: org.geoserver.web:gs-web-app (Maven), org.geoserver.main:gs-main (Maven). Ecosystems affected: Maven.

How do I fix GHSA-mc43-4fqr-c965?

Update org.geoserver.web:gs-web-app to 2.25.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mc43-4fqr-c965 is resolved across your whole dependency graph.

How do I detect GHSA-mc43-4fqr-c965 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.geoserver.web:gs-web-app. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-mc43-4fqr-c965 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-mc43-4fqr-c965?

O3 pinpoints whether GHSA-mc43-4fqr-c965 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-mc43-4fqr-c965 actively exploited in the wild?

No public exploit code has been indexed for GHSA-mc43-4fqr-c965 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-mc43-4fqr-c965?

GHSA-mc43-4fqr-c965 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 17th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was GHSA-mc43-4fqr-c965 published, and has it been updated?

GHSA-mc43-4fqr-c965 was published on June 10, 2025 and was last updated on June 10, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

GHSA-mc43-4fqr-c965

CRITICAL

GeoServer has improper ENTITY_RESOLUTION_ALLOWLIST URI validation in XML Processing (SSRF)

Also known asCVE-2024-34711

Published

Jun 10, 2025

Updated

Jun 10, 2025

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk17th percentile-0.16%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

2 pkgs affected

☕org.geoserver.web:gs-web-app☕org.geoserver.main:gs-main

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Summary

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. Attacker can abuse this to scan internal networks and gain information about them then exploit further. Moreover, attacker can read limited .xsd file on system.

Details

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.

Impact

An unauthenticated attacker can:

Scan internal network to gain insight about it and exploit further.
SSRF to endpoint ends with .xsd.
Read limited .xsd file on system.

Mitigation

Define the system property ENTITY_RESOLUTION_ALLOWLIST to limit the supported external schema locaitons.
The built-in allow list covers the locations required for the operation of OGC web services: www.w3.org,schemas.opengis.net,www.opengis.net,inspire.ec.europa.eu/schemas.
The user guide provides details on how to add additional locations (this is required for app-schema plugin where a schema is supplied to define an output format).

Resolution

GeoServer 2.25.0 and greater default to the use of ENTITY_RESOLUTION_ALLOWLIST and does not require you to provide a system property.
The use of ENTITY_RESOLUTION_ALLOWLIST is still supported if you require additional schema locations to be supported beyond the built-in allow list.
GeoServer 2.25.1 change ENTITY_RESOLUTION_ALLOWLIST no longer supports regular expressions

References

External Entities Resolution (GeoServer User Guide)

Credits

Le Mau Anh Phong from VNG Security Response Center & VNUHCM - University of Information Technology

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.geoserver.web:gs-web-app`	all versions	2.25.0
☕Maven	`org.geoserver.main:gs-main`	all versions	2.25.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.geoserver.web:gs-web-app. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.geoserver.web:gs-web-app to 2.25.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mc43-4fqr-c965 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-mc43-4fqr-c965 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-mc43-4fqr-c965. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary 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. Attacker can abuse this to scan internal networks and gain information about them then exploit further. Moreover, attacker can read limited `.xsd` file on system. ### Details 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 ch

O3 Security · Impact-Aware SCA

Is GHSA-mc43-4fqr-c965 in your dependencies?

O3 detects GHSA-mc43-4fqr-c965 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works