# CVE-2022-24847: Improper Input Validation in GeoServer

> An authenticated admin can trigger arbitrary code execution via unsafe JNDI lookups in GeoServer's security or configuration mechanisms.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Apr 2022
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-4pm3-f52j-8ggh

## What is CVE-2022-24847?

CVE-2022-24847 is a high-severity unsafe deserialization vulnerability in geoserver, published on 13 Apr 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

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.

Weakness: CWE-917 (Improper Neutralization of Special Elements used in an Expression Language Statement), CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2022-24847?

4 open source packages ship an affected version, including org.geoserver:gs-main. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.geoserver:gs-main` | Maven | All versions | 2.19.6 |
| `org.geoserver:gs-main` | Maven | All versions | 2.19.6 |
| `org.geoserver:gs-main` | Maven | From 2.20.0 | 2.20.4 |
| `org.geoserver:gs-main` | Maven | From 2.20.0 | 2.20.4 |

Products: Osgeo Geoserver.

## How do I fix CVE-2022-24847?

Upgrade org.geoserver:gs-main to a fixed version for your release line: 2.19.6 or 2.20.4.

## Is CVE-2022-24847 being exploited?

There is no known exploitation of CVE-2022-24847 in the wild and no public exploit code.

## Other vulnerabilities in geoserver

- [CVE-2023-25157](https://insights.sbomify.com/CVE-2023-25157/): Unfiltered SQL Injection Vulnerabilities in Geoserver (critical 9.8)
- [CVE-2024-34711](https://insights.sbomify.com/CVE-2024-34711/): GeoServer has improper ENTITY_RESOLUTION_ALLOWLIST URI validation in XML Processing (SSRF) (critical 9.3)
- [CVE-2023-41339](https://insights.sbomify.com/CVE-2023-41339/): Unsecured WMS dynamic styling sld=<url> parameter affords blind unauthenticated SSRF in GeoServer (high 8.6)
- [CVE-2023-43795](https://insights.sbomify.com/CVE-2023-43795/): WPS Server Side Request Forgery in GeoServer (high 8.6)
- [CVE-2024-29198](https://insights.sbomify.com/CVE-2024-29198/): GeoServer Vulnerable to Unauthenticated SSRF via TestWfsPost (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-24847 and fix it if it is affected.

What it is: CVE-2022-24847 is a high-severity unsafe deserialization vulnerability in geoserver, published on 13 Apr 2022. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-24847 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.geoserver:gs-main (Maven): affected all versions; fixed in 2.19.6
- org.geoserver:gs-main (Maven): affected all versions; fixed in 2.19.6
- org.geoserver:gs-main (Maven): affected from 2.20.0; fixed in 2.20.4
- org.geoserver:gs-main (Maven): affected from 2.20.0; fixed in 2.20.4

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-24847/ (Markdown: https://insights.sbomify.com/CVE-2022-24847/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-24847
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-24847
- OSV: https://osv.dev/vulnerability/CVE-2022-24847

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-24847/
Summaries are generated and may contain mistakes; the official description above is the record.