CVE-2024-8099
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 · uneditedA Server-Side Request Forgery (SSRF) vulnerability exists in the latest version of vanna-ai/vanna when using DuckDB as the database. An attacker can exploit this vulnerability by submitting crafted SQL queries that leverage DuckDB's default features, such as `read_csv`, `read_csv_auto`, `read_text`, and `read_blob`, to make unauthorized requests to internal or external resources. This can lead to unauthorized access to sensitive data, internal systems, and potentially further attacks.
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 confidenceThis is an SSRF vulnerability in vanna-ai/vanna where DuckDB's built-in file reading functions (`read_csv`, `read_csv_auto`, `read_text`, `read_blob`) can be leveraged through SQL queries to make arbitrary HTTP requests to internal or external resources. An attacker can abuse these default DuckDB features to bypass network boundaries and access sensitive services or data.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Identify vanna installation and versionRun 'pip show vanna' or check your project's dependency file (requirements.txt, pyproject.toml) for the installed vanna versionAffected if The installed version is any version of vanna that supports DuckDB backend prior to being patched
-
Confirm DuckDB is the active database backendInspect your vanna configuration or initialization code to verify DuckDB is being used as the SQL database (check for 'duckdb' in connection strings or backend settings)Affected if DuckDB is configured as the SQL backend for vanna
-
Verify DuckDB network functions are availableExecute a test SQL query through vanna using: SELECT * FROM read_csv('http://example.com/test.csv') to see if HTTP requests can be initiated from the databaseAffected if The query executes successfully and attempts an HTTP request, indicating the functions are not blocked
-
Check for SQL input validation layerReview your application code that passes queries to vanna's SQL execution layer to see if any input validation, sanitization, or query allow-listing is implemented before queries reach DuckDBAffected if No input validation exists and arbitrary SQL can be passed directly to DuckDB through vanna
-
Inspect DuckDB configuration for network restrictionsCheck if DuckDB is configured with disabled network access (duckdb_config with httpfs disabled or network access settings restricted) by querying DuckDB's settingsAffected if Network access is not explicitly disabled in DuckDB configuration
You are affected if you use vanna with DuckDB as the SQL backend and the read_csv/read_csv_auto/read_text/read_blob functions can execute HTTP requests without validation or restrictions.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataDisable or restrict DuckDB's file reading and HTTP request functions (`read_csv`, `read_csv_auto`, `read_text`, `read_blob`) when using vanna with untrusted input, and implement strict input validation on all SQL queries before execution.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-8099 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-8099 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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