ghsa-g9ph-j5vj-f8wm
Vulnerability from github
6.8 (Medium) - CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Impact
There are a number of CKAN plugins, including XLoader, DataPusher, Resource proxy and ckanext-archiver, that work by downloading the contents of local or remote files in order to perform some actions with their contents (e.g. pushing to the DataStore, streaming contents or saving a local copy). All of them use the resource URL, and there are currently no checks to limit what URLs can be requested. This means that a malicious (or unaware) user can create a resource with a URL pointing to a place where they should not have access in order for one of the previous tools to retrieve it (known as a Server Side Request Forgery).
Patches and Workarounds
Users wanting to protect against these kinds of attacks can use one or a combination of the following approaches:
- Use a separate HTTP proxy like Squid that can be used to allow / disallow IPs, domains etc as needed, and make CKAN extensions aware of this setting via the
ckan.download_proxy
config option. - Implement custom firewall rules to prevent access to restricted resources.
- Use custom validators on the resource
url
field to block/allow certain domains or IPs.
All latest versions of the plugins linked above support the ckan.download_proxy
settings. Support for this setting in the Resource Proxy plugin was included in CKAN 2.10.5 and 2.11.0
References
- Blog post provides more details on how to configure a Squid proxy to prevent these issues
{ "affected": [ { "package": { "ecosystem": "PyPI", "name": "ckan" }, "ranges": [ { "events": [ { "introduced": "0" }, { "fixed": "2.10.5" } ], "type": "ECOSYSTEM" } ] } ], "aliases": [ "CVE-2024-43371" ], "database_specific": { "cwe_ids": [ "CWE-918" ], "github_reviewed": true, "github_reviewed_at": "2024-08-21T18:27:11Z", "nvd_published_at": "2024-08-21T15:15:09Z", "severity": "MODERATE" }, "details": "### Impact\n\nThere are a number of CKAN plugins, including [XLoader](https://github.com/ckan/ckanext-xloader), [DataPusher](https://github.com/ckan/datapusher), [Resource proxy](https://docs.ckan.org/en/latest/maintaining/data-viewer.html#resource-proxy) and [ckanext-archiver](https://github.com/ckan/ckanext-archiver/), that work by downloading the contents of local or remote files in order to perform some actions with their contents (e.g. pushing to the DataStore, streaming contents or saving a local copy). All of them use the resource URL, and there are currently no checks to limit what URLs can be requested. This means that a malicious (or unaware) user can create a resource with a URL pointing to a place where they should not have access in order for one of the previous tools to retrieve it (known as a [Server Side Request Forgery](https://owasp.org/www-community/attacks/Server_Side_Request_Forgery)).\n\n### Patches and Workarounds\n\nUsers wanting to protect against these kinds of attacks can use one or a combination of the following approaches:\n\n* Use a separate HTTP proxy like [Squid](https://www.squid-cache.org/) that can be used to allow / disallow IPs, domains etc as needed, and make CKAN extensions aware of this setting via the [`ckan.download_proxy`](https://docs.ckan.org/en/latest/maintaining/configuration.html#ckan-download-proxy) config option. \n* Implement custom firewall rules to prevent access to restricted resources.\n* Use custom validators on the resource `url` field to block/allow certain domains or IPs.\n\nAll latest versions of the plugins linked above support the `ckan.download_proxy` settings. Support for this setting in the Resource Proxy plugin was included in CKAN 2.10.5 and 2.11.0\n\n### References\n\n* [Blog post](https://feeding.cloud.geek.nz/posts/restricting-outgoing-webapp-requests-using-squid-proxy/) provides more details on how to configure a Squid proxy to prevent these issues\n", "id": "GHSA-g9ph-j5vj-f8wm", "modified": "2024-08-21T18:27:12Z", "published": "2024-08-21T18:27:11Z", "references": [ { "type": "WEB", "url": "https://github.com/ckan/ckan/security/advisories/GHSA-g9ph-j5vj-f8wm" }, { "type": "ADVISORY", "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-43371" }, { "type": "WEB", "url": "https://github.com/ckan/ckan/commit/382beaec98cb331f2a030459ef043c50eaf5ad53" }, { "type": "WEB", "url": "https://github.com/ckan/ckan/commit/8601183cc2fc87277ea5b33ff75c3a5610812ab5" }, { "type": "PACKAGE", "url": "https://github.com/ckan/ckan" } ], "schema_version": "1.4.0", "severity": [ { "score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:N/A:N", "type": "CVSS_V3" }, { "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N", "type": "CVSS_V4" } ], "summary": "Potential access to sensitive URLs via CKAN extensions (SSRF)" }
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.