# CVE-2023-42439: GeoNode SSRF Bypass to return internal host data

> Attackers can bypass SSRF controls to read data from internal network services via URL parsing tricks.

- **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:** Yes
- **Published:** 15 Sep 2023
- **Updated:** 25 Sep 2024
- **Also known as:** GHSA-pxg5-h34r-7q8p, PYSEC-2023-176

## What is CVE-2023-42439?

CVE-2023-42439 is a high-severity server-side request forgery vulnerability in geonode, published on 15 Sep 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

GeoNode is an open source platform that facilitates the creation, sharing, and collaborative use of geospatial data. A SSRF vulnerability exists starting in version 3.2.0, bypassing existing controls on the software. This can allow a user to request internal services for a full read SSRF, returning any data from the internal network. The application is using a whitelist, but the whitelist can be bypassed. The bypass will trick the application that the first host is a whitelisted address, but the browser will use `@` or `%40` as a credential to the host geoserver on port 8080, this will return the data to that host on the response. Version 4.1.3.post1 is the first available version that contains a patch.

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

## Which versions are affected by CVE-2023-42439?

3 open source packages ship an affected version, including geonode and GeoNode. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `geonode` | PyPI | From 3.2.0 | None |
| `geonode` | PyPI | From 3.2.0 | 4.1.3.post1 |
| `GeoNode` | PyPI | From 3.2.0 | 4.1.3.post1 |

Products: Geosolutionsgroup Geonode.

## How do I fix CVE-2023-42439?

Upgrade geonode to 4.1.3.post1 or later.

## Is CVE-2023-42439 being exploited?

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

## Other vulnerabilities in geonode

- [CVE-2023-40017](https://insights.sbomify.com/CVE-2023-40017/): Geonode Server Side Request Forgery vulnerability (high 7.5)
- [CVE-2023-28442](https://insights.sbomify.com/CVE-2023-28442/): Geoserver for GeoNode sensitive information leak (high 7.5)
- [CVE-2023-26043](https://insights.sbomify.com/CVE-2023-26043/): XML External Entity (XXE) injection in GeoServer style upload functionality (medium 6.5)
- [CVE-2024-27091](https://insights.sbomify.com/CVE-2024-27091/): GeoNode stored XSS to full account takeover (medium 6.1)
- [CVE-2026-39921](https://insights.sbomify.com/CVE-2026-39921/): GeoNode < 4.4.5, 5.0.2 SSRF via Document Upload (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-42439 and fix it if it is affected.

What it is: CVE-2023-42439 is a high-severity server-side request forgery vulnerability in geonode, published on 15 Sep 2023. 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-2023-42439 exists.

Affected packages and fixed versions:
- geonode (PyPI): affected from 3.2.0; no fix listed
- geonode (PyPI): affected from 3.2.0; fixed in 4.1.3.post1
- GeoNode (PyPI): affected from 3.2.0; fixed in 4.1.3.post1

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

## Sources

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

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