dbcve.org
GeowebcacheApplication · Geoserver

CVE-2022-24846

HIGH · 7.2 CVSS v3.1 Published 2022-04-14
Fix available
A fix is available. Upgrade to 1.19.3 / 1.20.2 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
GeoWebCache is a tile caching server implemented in Java. The GeoWebCache disk quota mechanism can perform an unchecked JNDI lookup, which in turn can be used to perform class deserialization and result in arbitrary code execution. While in GeoWebCache the JNDI strings are provided via local configuration file, in GeoServer a user interface is provided to perform the same, that can be accessed remotely, and requires admin-level login to be used. These lookup are unrestricted in scope and can lead to code execution. The lookups are going to be restricted in GeoWebCache 1.21.0, 1.20.2, 1.19.3.

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

GeoWebCache contains an unchecked JNDI lookup vulnerability in its disk quota mechanism. Attackers can exploit this to perform class deserialization, leading to arbitrary code execution. In GeoServer, the attack surface is exposed through the admin UI, which requires admin-level authentication but can be accessed remotely.

MitigationUpgrade GeoWebCache to version 1.21.0, 1.20.2, or 1.19.3 (or corresponding GeoServer versions). Restrict admin UI access and implement network segmentation to limit exposure.

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
GeowebcacheApplication
Affected:< 1.19.3>= 1.20.0, < 1.20.2

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 GeoWebCache or GeoServer installation
    Locate the installed application - GeoWebCache is often deployed as a standalone web application (geowebcache.war) or bundled with GeoServer. Check for geowebcache or geoserver directories in your application server's webapps folder, or look for the geowebcache.jar/geoserver.jar files.
    Affected if GeoWebCache or GeoServer is present in the environment
  2. Determine installed version
    Check the version of GeoWebCache or GeoServer. For standalone GeoWebCache, look in the about页面或WAR文件中的版本文件. For GeoServer bundled with GeoWebCache, check the GeoServer version and cross-reference with the GeoWebCache version included in that release.
    Affected if The installed version is less than 1.19.3, OR greater than or equal to 1.20.0 but less than 1.20.2
  3. Check admin UI exposure
    Determine if the GeoWebCache or GeoServer admin interface is accessible over the network. Review web server or firewall configurations to see if the /geowebcache or /geoserver admin endpoints are exposed to untrusted networks.
    Affected if The admin UI is accessible from remote or untrusted networks
  4. Verify disk quota feature is configured
    Examine the GeoWebCache configuration for disk quota settings. Check geowebcache.xml or the disk quota configuration section in the admin UI to see if quota enforcement is enabled.
    Affected if Disk quota feature is enabled in the configuration

The environment is affected if GeoWebCache (standalone or bundled with GeoServer) version is below 1.19.3, or between 1.20.0 and 1.20.2, AND the admin UI is network-accessible, AND disk quota is configured.

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 1.19.3 / 1.20.2 or later
Fixed in 1.19.31.20.2
Interim mitigation

Upgrade GeoWebCache to version 1.21.0, 1.20.2, or 1.19.3 (or corresponding GeoServer versions). Restrict admin UI access and implement network segmentation to limit exposure.

Recommended fix High confidence

GeoWebCache 1.19.3, 1.20.2, or 1.21.0+ (depending on current branch)

  1. Identify current GeoWebCache version by checking the deployed WAR or pom.xml
  2. Determine which branch is in use (1.19.x, 1.20.x, or newer)
  3. Download the appropriate fixed release: GeoWebCache 1.19.3, 1.20.2, or 1.21.0+ from the official GeoWebCache GitHub releases
  4. Replace the existing GeoWebCache WAR file or update the dependency in the project
  5. Restart the GeoWebCache or GeoServer service
  6. Verify the upgrade by checking the version information in the GeoWebCache admin interface

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

Fix this in Geowebcache Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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