---
id: CVE-2023-40017
aliases:
  - GHSA-rmxg-6qqf-x8mr
  - PYSEC-2023-269
title: GeoNode Server Side Request forgery
summary: GeoNode Server Side Request forgery
severity: high
cvss: 7.5
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N'
vendor: geonode
product: geonode
ecosystem: pip
affected:
  - 'geonode >= 3.2.0, < 4.2.0'
patched:
  - geonode 4.2.0
published: '2024-11-21'
updated: '2026-09-10'
sourceUpdated: '2026-09-10T03:50:21.063557056Z'
source: OSV
sourceUrl: 'https://osv.dev/vulnerability/GHSA-rmxg-6qqf-x8mr'
references:
  - url: 'https://github.com/GeoNode/geonode/security/advisories/GHSA-rmxg-6qqf-x8mr'
  - url: 'https://nvd.nist.gov/vuln/detail/CVE-2023-40017'
  - url: >-
      https://github.com/GeoNode/geonode/commit/a9eebae80cb362009660a1fd49e105e7cdb499b9
  - url: 'https://github.com/GeoNode/geonode'
  - url: >-
      https://github.com/pypa/advisory-database/tree/main/vulns/geonode/PYSEC-2023-269.yaml
tags:
  - osv
  - pip
epss: 0.00763
epssPercentile: 0.53413
ingestedAt: '2026-09-12T03:13:01.726Z'
---

## Overview

### Summary
A server side request forgery vuln was found within geonode when testing on a bug bounty program. Server side request forgery allows a user to request information on the internal service/services.

### Details
The endpoint /proxy/?url= does not properly protect against SSRF. when using the following format you can request internal hosts and display data. /proxy/?url=http://169.254.169.254\@whitelistedIPhere. This will state wether the AWS internal IP is alive. If you get a 404, the host is alive. A non alive host will not display a response. To display metadata, use a hashfrag on the url /proxy/?url=http://169.254.169.254\@#whitelisteddomain.com or try   /proxy/?url=http://169.254.169.254\@%23whitelisteddomain.com

### Impact
Port scan internal hosts, and request information from internal hosts.


## Affected packages

- `geonode >= 3.2.0, < 4.2.0`

## Remediation

Upgrade to a patched release:

- `geonode 4.2.0`