dbcve.org
CkanApplication · Okfn

CVE-2024-43371

MEDIUM · 6.5 CVSS v3.1 Published 2024-08-21
Fix available
A fix is available. Upgrade to 2.10.5 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
CKAN is an open-source data management system for powering data hubs and data portals. 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). Users wanting to protect against these kinds of attacks can use one or a combination of the following approaches: (1) 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. (2) Implement custom firewall rules to prevent access to restricted resources. (3) Use custom validators on the resource url field to block/allow certain domains or IPs. All latest versions of the plugins listed 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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

CKAN is vulnerable to Server Side Request Forgery (SSRF) due to multiple plugins (XLoader, DataPusher, Resource proxy, ckanext-archiver) downloading content from user-provided URLs without validation. A malicious user can create a resource with a URL pointing to internal services, restricted networks, or cloud metadata endpoints, causing the server to retrieve content on their behalf.

MitigationConfigure the ckan.download_proxy setting to route requests through a controlled HTTP proxy (e.g., Squid) with IP/domain restrictions, or implement firewall rules and custom URL validators to restrict accessible destinations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CkanApplication
Affected:< 2.10.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check CKAN version
    Run `ckan --version` or inspect the installed package version via `pip show ckan`
    Affected if The installed version is below 2.10.5 (e.g., 2.10.4, 2.10.0, 2.9.x, etc.)
  2. Identify enabled plugins
    Review the `ckan.plugins` setting in your CKAN configuration file (typically in `/etc/ckan/default/production.ini` or `ckan.ini`)
    Affected if Any of these plugins are listed: xloader, datapusher, resource_proxy, or archiver (ckanext-archiver)
  3. Verify download_proxy setting
    Check the CKAN configuration file for the `ckan.download_proxy` setting
    Affected if The setting is absent, commented out, or not configured to a controlled proxy server
  4. Confirm plugin URLs are user-controlled
    In the CKAN web interface, verify that resource creation allows arbitrary URL input, or check API endpoints that accept URL parameters for resource creation
    Affected if Users can create resources with custom URLs pointing to external sources without validation

You are affected if running CKAN version below 2.10.5 with any of the vulnerable plugins (XLoader, DataPusher, Resource proxy, archiver) enabled, and without ckan.download_proxy configured as a mitigating proxy.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.10.5 or later
Fixed in 2.10.5
Interim mitigation

Configure the ckan.download_proxy setting to route requests through a controlled HTTP proxy (e.g., Squid) with IP/domain restrictions, or implement firewall rules and custom URL validators to restrict accessible destinations.

Recommended fix High confidence

CKAN 2.10.5 or 2.11.0

  1. Upgrade CKAN to version 2.10.5 or later (2.11.0 recommended)
  2. After upgrade, configure ckan.download_proxy in your CKAN configuration file (e.g., production.ini) to point to a secure HTTP proxy like Squid
  3. Restart CKAN services to apply the configuration
  4. Verify the download_proxy setting is active by testing resource downloads
Caveat Minor - adding new config option; no database changes required

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ckan Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-43371 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-43371 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data