First published: Fri Sep 15 2023(Updated: )
A SSRF vulnerability exists, 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 with @ and encoded value of @ (%40) GET /proxy/?url=http://development.demo.geonode.org%40geoserver:8080/geoserver/web This 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. ![image](https://user-images.githubusercontent.com/35967437/264379628-8cecbc56-be6c-49dc-abe8-0baf8b8695cc.png)
Credit: security-advisories@github.com security-advisories@github.com security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
pip/GeoNode | >=3.2.0<=4.1.2 | 4.1.3.post1 |
Geosolutionsgroup Geonode | >=3.2.0 | |
Geosolutionsgroup Geonode | >=3.2.0<4.1.3 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The CVE ID of this vulnerability is CVE-2023-42439.
The severity of CVE-2023-42439 is high with a CVSS score of 6.5.
The affected software is GeoNode version 3.2.0 up to 4.1.2.
CVE-2023-42439 is a SSRF vulnerability in GeoNode that allows bypassing existing controls and can be used to request internal services for a full read SSRF, returning any data from the internal network.
To fix CVE-2023-42439, upgrade to GeoNode version 4.1.3 or later.