CVE-2024-9617
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 · uneditedAn IDOR vulnerability in danswer-ai/danswer v0.3.94 allows an attacker to view any files. The application does not verify whether the attacker is the creator of the file, allowing the attacker to directly call the GET /api/chat/file/{file_id} interface to view any user's file.
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 confidenceAn IDOR vulnerability in danswer-ai/danswer v0.3.94 allows unauthorized access to files via the GET /api/chat/file/{file_id} endpoint. The application fails to verify that the requester is the creator of the file, enabling any authenticated user to view any other user's files by simply knowing or guessing the file ID.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 danswer versionCheck the installed danswer-ai/danswer version by inspecting package metadata, docker image tags, or the running application version endpoint (often at /api/version or similar). Compare against v0.3.94.Affected if Running version v0.3.94 specifically
-
Confirm endpoint availabilityVerify the GET /api/chat/file/{file_id} endpoint exists in the application by checking API route definitions or attempting a request (with valid auth) to a known file ID.Affected if The /api/chat/file/{file_id} endpoint is accessible and responds to requests
-
Inspect authorization logicReview the source code or configuration for the file endpoint handler. Look for user ownership validation before returning file contents. Check if user-session context is compared against file ownership records.Affected if No ownership validation is performed before serving file content, or the check is missing/disabled
-
Test cross-user file accessWith two different authenticated user accounts, create a file as User A, obtain its file ID, then attempt to access that same file ID while authenticated as User B.Affected if User B can successfully retrieve User A's file content without receiving a 403 Forbidden or ownership error
-
Check authentication requirementsVerify whether the file endpoint requires authentication at all, or if it can be accessed anonymously.Affected if The endpoint accepts requests without valid authentication or session context
You are affected if running danswer v0.3.94 AND the /api/chat/file/{file_id} endpoint exists AND allows any authenticated user to access files they do not own.
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 dataImplement proper authorization checks to verify that the requesting user is the owner of the file before returning file contents. This should include validating user-session context against file ownership records.
- Consultation1.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-9617 — 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-9617 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