CVE-2023-40017High· 7.5▾ TwilightGeoNode Server Side Request forgery
▾ Twilight zone — High severity, or a signal on a lesser flaw
impact 41.3 · likelihood 0.2 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Exploit-prediction probability, daily snapshots since Sep 12.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
Last analysed / modified upstream
0.8%
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.
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
Port scan internal hosts, and request information from internal hosts.
geonode >= 3.2.0, < 4.2.0Upgrade to a patched release:
geonode 4.2.0Connected by shared product, vendor, weakness, or advisory.
CVE-2023-42439High· 7.5GeoNode vulnerable to SSRF Bypass to return internal host data
CVE-2023-26043Medium· 6.5GeoServer style upload functionality vulnerable to XML External Entity (XXE) injection
CVE-2026-39921Medium· 6.3GeoNode versions 4.0 before 4.4.5 and 5.0 before 5.0.2 contain a server-side request forgery vulnerability that allows authenticated user…
CVE-2024-27091Medium· 6.1GeoNode: Stored XSS to full account takeover
CVE-2026-39922Medium· 6.3GeoNode contains a server-side request forgery vulnerability in the service registration endpoint