← Back
CVE-2024-41675

Cross-Site Scripting (XSS) in ckan (CVE-2024-41675)

Summary

cross-site scripting in ckan (CVE-2024-41675). Confidential information can be exposed externally. Exploitable via ``datatables_view``. Mitigation: upgrade to `2.10.5` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2024-41675** has been found in ckan. Attackers can target a specific entry point like ``datatables_view`` over the network to misuse the product. Confidential information can be exposed externally. CVSS score: ?/10. What to do: upgrade ckan to **2.10.5** or later. If unsure, ask your IT team or search "ckan CVE-2024-41675" on the vendor's site.
CVE-2024-41675 (ckan) — CWE-79 / Attack vector: remote (network-reachable) Attack surface: `datatables_view` Patched: `2.10.5` — apply immediately Workaround: Prevent importing of tabular files to the DataStore via DataPusher, XLoader,etc, at least those published from untrusted sources. Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs. Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**Cross-site scripting (XSS)** (CWE-79) exists in ckan. Attackers reach the vulnerable code path via ``datatables_view`` without authentication.
📍 Affected scope
ckan — . Attack surface: `datatables_view`.
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to **2.10.5**.
🛡️ Workaround
Workaround: Prevent importing of tabular files to the DataStore via DataPusher, XLoader,etc, at least those published from untrusted sources.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'ckan' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response Actions (7 steps)

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'ckan' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `ckan` を grep し、稼働しているサービス・バージョンを把握する。

  2. 5
    Apply temporary workaround mitigate
    Prevent importing of tabular files to the DataStore via DataPusher, XLoader,etc, at least those published from untrusted sources.

    パッチが適用されるまでの応急処置として、Prevent importing of tabular files to the DataStore via DataPusher, XLoader,etc, at least those published from untrusted sources. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 6
    Apply patch patch
    Upgrade ckan to 2.10.5

    ステージング環境で 2.10.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。

  4. 7
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

PyPI ckan
[{"type":"ECOSYSTEM","events":[{"introduced":"2.7.0"},{"fixed":"2.10.5"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →