geonode
Affected
- introduced
3.2.0, fixed4.2.0(ecosystem)
Fixed versions
4.2.0
Fix
- Fixed version
4.2.0pip install --upgrade geonode==4.2.0
Advisory
Also known as: CVE-2023-40017, PYSEC-2023-269
GeoNode Server Side Request forgery
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.
High Basis: The source's own band: HIGH
3.2.0, fixed 4.2.0 (ecosystem)4.2.0
4.2.0pip install --upgrade geonode==4.2.0Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0