sniff_csv provides filesystem access even when enable_external_access is disabled in duckdb
CVE-2024-41672GHSA-w2gf-jxc9-pf2q
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (duckdb 1.1.0), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
PyPI duckdb
- Affected
- >= 1.0.0, < 1.1.0
- Fixed in
- 1.1.0
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-w2gf-jxc9-pf2q lists affected ranges: PyPI duckdb >=1.0.0 <1.1.0 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-w2gf-jxc9-pf2q lists affected ranges: PyPI duckdb >=1.0.0 <1.1.0
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- EPSS
- CVE-2024-41672: 0.81% estimated exploitation activity in the next 30 days; percentile 57.05 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary Content in filesystem is accessible for reading using sniffcsv, even with enableexternalaccess=false. Details During a pentest, a security researcher was able to access environment variable data and other system data by using the sniffcsv function, even though we set enableexternalaccess to false. PoC Impact Provides an attacker with access to filesystem even when access is expected to be disabled and other similar functions do NOT provide access. For example select from readcsv('/proc/self/environ') fails with a permission error. There seems to be two vectors to this vulnerability: 1. Access to files that should otherwise not be allowed. (We expect Permission Error: Scanning CSV files is disabled through configuration and not to provide any access to the file or even acknowledge that it exists). 2. The content from a (non-csv?) file can be read (e.g. /etc/hosts, proc/self/environ, etc) even though that doesn't seem to be the intent of the sniffcsv function (my understanding…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-w2gf-jxc9-pf2q
- Revision 1 · created ·
Published from osv record GHSA-w2gf-jxc9-pf2q
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2024-41672 Advisory: sniff_csv provides filesystem access even when enable_external_access is disabled in duckdb IDs: CVE-2024-41672, GHSA-w2gf-jxc9-pf2q Record: https://patchnext.com/advisories/cve-2024-41672 (revision 2, source checked 26 Oct 2026, 13:30 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 7.5) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: duckdb 1.1.0. A vendor fix does not mean a deployment is fixed. ## Affected components - PyPI duckdb: affected >= 1.0.0, < 1.1.0; fixed in 1.1.0 ## Suggested inspection (read-only) - `python -m pip show duckdb`: prints the installed version. Run with the environment that serves production active. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on duckdb. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-w2gf-jxc9-pf2q (OSV record GHSA-w2gf-jxc9-pf2q lists affected ranges: PyPI duckdb >=1.0.0 <1.1.0 (fixed)) - Verified: https://github.com/advisories/GHSA-w2gf-jxc9-pf2q (GitHub-reviewed advisory GHSA-w2gf-jxc9-pf2q lists affected ranges: PyPI duckdb >=1.0.0 <1.1.0) Commands are suggestions: review each one before running it.
Loading voting…