---
id: CVE-2024-43371
aliases:
  - GHSA-g9ph-j5vj-f8wm
  - PYSEC-2026-1252
title: Potential access to sensitive URLs via CKAN extensions (SSRF)
summary: Potential access to sensitive URLs via CKAN extensions (SSRF)
severity: medium
cvss: 4.5
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:N/A:N'
vendor: ckan
product: ckan
ecosystem: pip
affected:
  - ckan < 2.10.5
patched:
  - ckan 2.10.5
published: '2024-08-21'
updated: '2026-07-07'
source: OSV
sourceUrl: 'https://osv.dev/vulnerability/GHSA-g9ph-j5vj-f8wm'
references:
  - url: 'https://github.com/ckan/ckan/security/advisories/GHSA-g9ph-j5vj-f8wm'
  - url: 'https://nvd.nist.gov/vuln/detail/CVE-2024-43371'
  - url: >-
      https://github.com/ckan/ckan/commit/382beaec98cb331f2a030459ef043c50eaf5ad53
  - url: >-
      https://github.com/ckan/ckan/commit/8601183cc2fc87277ea5b33ff75c3a5610812ab5
  - url: 'https://github.com/ckan/ckan'
tags:
  - osv
  - pip
epss: 0.00369
epssPercentile: 0.30766
ingestedAt: '2026-07-08T18:25:49.697Z'
---

## Overview

### Impact

There 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)).

### 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](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. 
* 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](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


## Affected packages

- `ckan < 2.10.5`

## Remediation

Upgrade to a patched release:

- `ckan 2.10.5`