First published: Thu Aug 24 2023(Updated: )
### 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.
Credit: security-advisories@github.com security-advisories@github.com security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
Geosolutionsgroup Geonode | >=3.2.0<=4.1.2 | |
pip/geonode | >=3.2.0<4.2.0 | 4.2.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2023-40017 is a vulnerability in GeoNode that allows server-side request forgery, potentially enabling an attacker to port scan internal hosts and request internal resources.
GeoNode is an open source platform for creating, sharing, and collaborating on geospatial data.
Versions 3.2.0 through 4.1.2 of GeoNode are affected by CVE-2023-40017.
CVE-2023-40017 has a severity rating of high (7.5).
To fix CVE-2023-40017, it is recommended to update GeoNode to a version that includes the fix or apply the necessary patch provided by the product vendor.