GeoNode Server Side Request forgery
🔗 CVE IDs covered (1)
📋 Description
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 products1
- pip/geonode:>= 3.2.0, < 4.2.0
🔗 References (5)
- https://github.com/GeoNode/geonode/security/advisories/GHSA-rmxg-6qqf-x8mr
- https://nvd.nist.gov/vuln/detail/CVE-2023-40017
- https://github.com/GeoNode/geonode/commit/a9eebae80cb362009660a1fd49e105e7cdb499b9
- https://github.com/pypa/advisory-database/tree/main/vulns/geonode/PYSEC-2023-269.yaml
- https://github.com/advisories/GHSA-rmxg-6qqf-x8mr