dbcve.org
GeoserverApplication · Osgeo

CVE-2024-34711

HIGH · 8.2 CVSS v3.1 Published 2025-06-10
Fix available
A fix is available. Upgrade to 2.25.0 or later.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

GeoServer contains an improper URI validation vulnerability in its XML entity resolution. The regex (?i)(jar:file|http|vfs)[^?#;]*\.xsd used to filter URIs is too permissive, allowing attackers to make GET requests to arbitrary HTTP servers. This enables XXE attacks for internal network scanning and information disclosure.

MitigationUpgrade to GeoServer 2.25.0 or later which defaults to ENTITY_RESOLUTION_ALLOWLIST, or manually configure the entity resolution allowlist to restrict URI patterns.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GeoserverApplication
Affected:< 2.25.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed GeoServer version
    Access the GeoServer admin web interface, go to 'About' > 'Version' page, or check the GeoServer startup logs for the version number.
    Affected if The installed version is lower than 2.25.0 (e.g., 2.24.x, 2.23.x, or earlier).
  2. Identify if XML entity resolution is in use
    Check GeoServer configuration files (typically in the data directory under 'security' or 'xml' directories) or inspect XML parsing settings. Review any custom XML parsers or XSLT transformations that may reference external entities.
    Affected if GeoServer is configured to process XML documents that could contain external entity references, particularly when loading styled layer descriptors, SLD files, or other XML-based configurations from untrusted sources.
  3. Inspect entity resolution allowlist configuration
    Locate the GeoServer configuration file (commonly 'web.xml' or 'geoserver.xml' in the data directory) and search for 'ENTITY_RESOLUTION' settings. Check for properties like 'ENTITY_RESOLUTION_ALLOWLIST' or similar URI validation settings.
    Affected if No allowlist is configured, the allowlist is empty, or the allowlist uses overly permissive patterns that include 'http:' URIs without strict domain restrictions.
  4. Review the applied URI validation regex
    Examine the XML parser or GeoServer configuration that handles external entity resolution. Look for regex patterns similar to '(?i)(jar:file|http|vfs)[^?#;]*\.xsd' in the codebase or configuration.
    Affected if The URI validation regex allows arbitrary HTTP URLs (contains 'http|' or 'http:') without strict domain or path constraints, enabling requests to arbitrary external servers.

A user is affected if they run GeoServer version below 2.25.0 with XML entity resolution enabled and without a properly configured allowlist that restricts URI patterns to trusted sources only.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.25.0 or later
Fixed in 2.25.0
Interim mitigation

Upgrade to GeoServer 2.25.0 or later which defaults to ENTITY_RESOLUTION_ALLOWLIST, or manually configure the entity resolution allowlist to restrict URI patterns.

Recommended fix High confidence

GeoServer 2.25.0 or later

  1. Backup your current GeoServer data directory and configuration
  2. Download GeoServer 2.25.0 or later from the official GeoServer website (https://geoserver.org/)
  3. Stop the running GeoServer instance
  4. Replace the GeoServer installation with the new version, preserving the data directory
  5. Start the new GeoServer instance
  6. Verify the version is 2.25.0 or later by checking the About > Version page in the GeoServer admin UI
  7. Confirm the ENTITY_RESOLUTION_ALLOWLIST is enabled by default (should be automatic in 2.25.0+)

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Geoserver Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-34711 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-34711 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data