← Back
CVE-2024-41672
Information Disclosure in duckdb (CVE-2024-41672)
Summary
vulnerability in duckdb (CVE-2024-41672). Confidential information can be exposed externally. Exploitable via ``sniff_csv``. Mitigation: upgrade to `1.1.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2024-41672** has been found in duckdb.
Attackers can target a specific entry point like ``sniff_csv`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: ?/10.
What to do: upgrade duckdb to **1.1.0** or later.
If unsure, ask your IT team or search "duckdb CVE-2024-41672" on the vendor's site.
CVE-2024-41672 (duckdb) — CWE-200 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `sniff_csv` / `enable_external_access` / `disabled_filesystems` / `main`
Patched: `1.1.0` — apply immediately
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
**information disclosure** (CWE-200) exists in duckdb. Attackers reach the vulnerable code path via ``sniff_csv`` without authentication.
📍 Affected scope
duckdb — . Attack surface: `sniff_csv` / `enable_external_access` / `disabled_filesystems` / `main`.
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to **1.1.0**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'duckdb' .` 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
-
1Identify exposure identify
grep -r 'duckdb' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `duckdb` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade duckdb to 1.1.0ステージング環境で 1.1.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
duckdb
[{"type":"ECOSYSTEM","events":[{"introduced":"1.0.0"},{"fixed":"1.1.0"}]}]
References
- advisory https://github.com/advisories/GHSA-w2gf-jxc9-pf2q
- advisory https://nvd.nist.gov/vuln/detail/CVE-2024-41672
- package https://github.com/duckdb/duckdb
- web https://github.com/duckdb/duckdb/security/advisories/GHSA-w2gf-jxc9-pf2q
- web https://github.com/duckdb/duckdb/commit/c9b7c98aa0e1cd7363fe8bb8543a95f38e980d8a
- web https://github.com/duckdb/duckdb/pull/13133
- web https://github.com/pypa/advisory-database/tree/main/vulns/duckdb/PYSEC-2024-203.yaml