cve.bz

CVE-2024-34711 osgeo geoserver: SSRF

8.2 highEPSS 0.3%Fix available

High (8.2) in osgeo geoserver. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in org.geoserver.web:gs-web-app 2.25.0.

On this page
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.

Severity

CVSS 3.1

8.2 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 24th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2025-06-10. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
CWE-611 Improper Restriction of XML External Entity Reference
CWE-918 Server-Side Request Forgery (SSRF)
OWASP Top 10
A01:2025 Broken Access Control, A02:2025 Security Misconfiguration
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

  • org.geoserver.web:gs-web-app (Maven): fixed in 2.25.0
  • org.geoserver.main:gs-main (Maven): fixed in 2.25.0

Ask an AI about this CVE

Show the promptExplain CVE-2024-34711 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2024-34711?via=ask-ai-copy and https://cve.bz/cve/CVE-2024-34711?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2024-34711 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
osgeo:geoserverbefore 2.25.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-mc43-4fqr-c965Mavenorg.geoserver.web:gs-web-app<2.25.02.25.0
GHSA-mc43-4fqr-c965Mavenorg.geoserver.main:gs-main<2.25.02.25.0

Attack patterns (CAPEC)

  • CAPEC-221 Data Serialization External Entities Blowup
  • CAPEC-664 Server Side Request Forgery Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-200 (59).

References

Check your stackJSON