CVE-2022-24847

Improper Input Validation in GeoServer

Workarounds

Protection can be achieved by making the GUI (geoserver/web), the REST configuration (geoserver/rest) and the embedded GeoWebCache configuration (geoserver/gwc/rest) unreachable from remote hosts, in addition to protecting access to the file system where the GeoServer configuration is stored.

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 application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.

CVE-2022-24847 has a CVSS score of 7.2 (High). The vector is network-reachable, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.20.4, 2.19.6); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

The lookups are going to be restricted in GeoServer 2.21.0, 2.20.4, 2.19.6.

1. What is CVE-2022-24847? CVE-2022-24847 is a high-severity improper input validation vulnerability in org.geoserver:gs-main (maven), affecting versions >= 2.20.0, < 2.20.4. It is fixed in 2.20.4, 2.19.6. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
2. How severe is CVE-2022-24847? CVE-2022-24847 has a CVSS score of 7.2 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of org.geoserver:gs-main are affected by CVE-2022-24847? org.geoserver:gs-main (maven) versions >= 2.20.0, < 2.20.4 is affected.
4. Is there a fix for CVE-2022-24847? Yes. CVE-2022-24847 is fixed in 2.20.4, 2.19.6. Upgrade to this version or later.
5. Is CVE-2022-24847 exploitable, and should I be worried? Whether CVE-2022-24847 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2022-24847 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2022-24847?
   • Upgrade org.geoserver:gs-main to 2.20.4 or later
   • Upgrade org.geoserver:gs-main to 2.19.6 or later

Other vulnerabilities in org.geoserver:gs-main