dbcve.org
GeoserverApplication · Osgeo

CVE-2022-24847

HIGH · 7.2 CVSS v3.1 Published 2022-04-13
Fix available
A fix is available. Upgrade to 2.19.6 / 2.20.4 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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 software server written in Java that allows users to share and edit geospatial data. The GeoServer security mechanism can perform an unchecked JNDI lookup, which in turn can be used to perform class deserialization and result in arbitrary code execution. The same can happen while configuring data stores with data sources located in JNDI, or while setting up the disk quota mechanism. In order to perform any of the above changes, the attack needs to have obtained admin rights and use either the GeoServer GUI, or its REST API. The lookups are going to be restricted in GeoServer 2.21.0, 2.20.4, 1.19.6. Users unable to upgrade should restrict access to the `geoserver/web` and `geoserver/rest` via a firewall and ensure that the GeoWebCache is not remotely accessible.

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 unchecked JNDI lookup vulnerability that allows authenticated administrators to trigger class deserialization through malicious JNDI references, resulting in arbitrary code execution. The flaw is present when configuring data stores with JNDI-based data sources or setting up the disk quota mechanism.

MitigationUpgrade to GeoServer 2.21.0, 2.20.4, or 1.19.6 which restrict JNDI lookups; alternatively, restrict firewall access to /geoserver/web and /geoserver/rest endpoints and ensure GeoWebCache is not remotely accessible.

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.19.6>= 2.20.0, < 2.20.4

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Identify GeoServer version
    Locate the geoserver.war file or check the application's about page (usually at /geoserver/about/version) to find the exact version number installed
    Affected if The version is less than 2.19.6, or greater than or equal to 2.20.0 but less than 2.20.4
  2. Inspect JNDI data store configurations
    Navigate to GeoServer admin UI: Data > Stores. Review each data store configuration. For each store, check if the 'jndiReferenceName' or similar JNDI connection parameter is populated with a value pointing to an external JNDI datasource
    Affected if Any data store is configured with a JNDI reference pointing to an external datasource
  3. Review disk quota settings
    Navigate to GeoServer admin UI: Settings > Disk Quota. Check if disk quota is enabled and configured with a JNDI-based cache directory or data source
    Affected if Disk quota is enabled with a JNDI reference configured
  4. Verify administrative access to vulnerable endpoints
    Confirm whether the /geoserver/web (web admin UI) and /geoserver/rest (REST API) endpoints are accessible to untrusted network segments or the public internet
    Affected if These administrative endpoints are accessible without proper network restrictions

A user is affected if their GeoServer version falls within the vulnerable range AND (JNDI data stores OR disk quota with JNDI) are configured, especially if admin endpoints are network-accessible.

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.19.6 / 2.20.4 or later
Fixed in 2.19.62.20.4
Interim mitigation

Upgrade to GeoServer 2.21.0, 2.20.4, or 1.19.6 which restrict JNDI lookups; alternatively, restrict firewall access to /geoserver/web and /geoserver/rest endpoints and ensure GeoWebCache is not remotely accessible.

Recommended fix High confidence

GeoServer 2.20.4 (or 2.19.6 for 2.19.x branch, or 2.21.0 for latest)

  1. 1. Back up your current GeoServer configuration and data directory
  2. 2. Download GeoServer 2.20.4 (or 2.19.6 if staying on the 2.19.x branch, or 2.21.0 if upgrading to the latest branch) from the official GeoServer distribution
  3. 3. Stop the running GeoServer instance
  4. 4. Replace the GeoServer web application (WAR file or exploded directory) with the new version
  5. 5. Ensure your data directory is pointing to the existing configuration (do not delete the data directory)
  6. 6. Start GeoServer and verify the REST API and admin GUI are functional
  7. 7. Confirm JNDI lookups are now restricted by testing that arbitrary JNDI lookups fail
Caveat Minor: Review any existing JNDI data source configurations as lookups are now restricted; ensure your JNDI resources are properly configured within the application server

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

Fix this in Geoserver Scoped from the published advisory
  • Consultation4.0 h
  • Implementation10.0 h
  • Testing6.0 h
  • Review / QA3.0 h
23.0 hours of engineering $4,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-24847 — 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-2022-24847 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