# CVE-2021-40822: GeoServer allows SSRF via the option for setting a proxy host

> Attackers can exploit a proxy host setting in GeoServer to perform Server-Side Request Forgery, potentially accessing internal resources.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 May 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-rr33-j5p5-ppf8

## What is CVE-2021-40822?

CVE-2021-40822 is a high-severity server-side request forgery vulnerability in n/a, published on 1 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

GeoServer through 2.18.5 and 2.19.x through 2.19.2 allows SSRF via the option for setting a proxy host.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2021-40822?

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 to 2.18.5 | None |
| `org.geoserver:gs-main` | Maven | All versions to 2.18.5 | None |
| `org.geoserver:gs-main` | Maven | From 2.19.0 to 2.19.2 | None |
| `org.geoserver:gs-main` | Maven | From 2.19.0 to 2.19.2 | None |

Products: Osgeo Geoserver.

## How do I fix CVE-2021-40822?

No fix has been published for CVE-2021-40822 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-40822 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-40822 exists.

Public exploit code:

- PoC and Dockerized vulnerable lab for CVE-2021-40822 (SSRF in GeoServer) (github_poc): https://github.com/phor3nsic/CVE-2021-40822
- Geoserver - Server-Side Request Forgery (nuclei): http/cves/2021/CVE-2021-40822.yaml

## Other vulnerabilities in n/a

- [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-2021-40822 and fix it if it is affected.

What it is: CVE-2021-40822 is a high-severity server-side request forgery vulnerability in n/a, published on 1 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-40822 exists.

Affected packages and fixed versions:
- org.geoserver:gs-main (Maven): affected all versions up to 2.18.5; no fix listed
- org.geoserver:gs-main (Maven): affected all versions up to 2.18.5; no fix listed
- org.geoserver:gs-main (Maven): affected from 2.19.0 up to 2.19.2; no fix listed
- org.geoserver:gs-main (Maven): affected from 2.19.0 up to 2.19.2; no fix listed

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-2021-40822/ (Markdown: https://insights.sbomify.com/CVE-2021-40822/index.md)
```

## Sources

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

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