pysec-2024-203
Vulnerability from pysec
DuckDB is a SQL database management system. In versions 1.0.0 and prior, content in filesystem is accessible for reading using sniff_csv
, even with enable_external_access=false
. This vulnerability provides an attacker with access to filesystem even when access is expected to be disabled and other similar functions do NOT provide access. There seem to be two vectors to this vulnerability. First, access to files that should otherwise not be allowed. Second, the content from a file can be read (e.g. /etc/hosts
, proc/self/environ
, etc) even though that doesn't seem to be the intent of the sniff_csv function. A fix for this issue is available in commit c9b7c98aa0e1cd7363fe8bb8543a95f38e980d8a and is expected to be part of version 1.1.0.
{ affected: [ { package: { ecosystem: "PyPI", name: "duckdb", purl: "pkg:pypi/duckdb", }, ranges: [ { events: [ { introduced: "0", }, { fixed: "c9b7c98aa0e1cd7363fe8bb8543a95f38e980d8a", }, { fixed: "c9b7c98aa0e1cd7363fe8bb8543a95f38e980d8a", }, ], repo: "https://github.com/duckdb/duckdb", type: "GIT", }, { events: [ { introduced: "0", }, { fixed: "1.1.0", }, ], type: "ECOSYSTEM", }, ], versions: [ "0.0.0", "0.0.2", "0.0.3", "0.1.0", "0.1.1", "0.1.2", "0.1.3", "0.1.5", "0.1.6", "0.1.7", "0.1.8", "0.1.9", "0.10.0", "0.10.1", "0.10.2", "0.10.3", "0.2.0", "0.2.1", "0.2.2", "0.2.3", "0.2.4", "0.2.5", "0.2.6", "0.2.7", "0.2.8", "0.2.9", "0.3.0", "0.3.1", "0.3.2", "0.3.3", "0.3.4", "0.4.0", "0.5.0", "0.5.1", "0.6.0", "0.6.1", "0.7.0", "0.7.1", "0.8.0", "0.8.1", "0.9.0", "0.9.1", "0.9.2", "1.0.0", ], }, ], aliases: [ "CVE-2024-41672", ], details: "DuckDB is a SQL database management system. In versions 1.0.0 and prior, content in filesystem is accessible for reading using `sniff_csv`, even with `enable_external_access=false`. This vulnerability provides an attacker with access to filesystem even when access is expected to be disabled and other similar functions do NOT provide access. There seem to be two vectors to this vulnerability. First, access to files that should otherwise not be allowed. Second, the content from a file can be read (e.g. `/etc/hosts`, `proc/self/environ`, etc) even though that doesn't seem to be the intent of the sniff_csv function. A fix for this issue is available in commit c9b7c98aa0e1cd7363fe8bb8543a95f38e980d8a and is expected to be part of version 1.1.0.", id: "PYSEC-2024-203", modified: "2025-01-19T19:18:58.299130+00:00", published: "2024-07-24T18:15:05+00:00", references: [ { type: "ADVISORY", url: "https://github.com/duckdb/duckdb/security/advisories/GHSA-w2gf-jxc9-pf2q", }, { type: "EVIDENCE", url: "https://github.com/duckdb/duckdb/security/advisories/GHSA-w2gf-jxc9-pf2q", }, { type: "FIX", url: "https://github.com/duckdb/duckdb/commit/c9b7c98aa0e1cd7363fe8bb8543a95f38e980d8a", }, { type: "FIX", url: "https://github.com/duckdb/duckdb/pull/13133", }, ], related: [ "GHSA-w2gf-jxc9-pf2q", "GHSA-w2gf-jxc9-pf2q", ], severity: [ { score: "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N", type: "CVSS_V3", }, ], }
Log in or create an account to share your comment.
This schema specifies the format of a comment related to a security advisory.
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.