CVE-2024-9617: danswer-ai/danswer · Insecure Direct Object Reference
Affects danswer-ai/danswerSource CVE Database V5
Not known to be exploited · public detection template (Nuclei) · CVSS 6.5 Medium.
Data as of 26 Oct 2026, 07:57 UTC
- EPSS
- 1.7% chance of exploitation in 30 days – higher than 77% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 20 Mar 2025
Detectable: evidence found.
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubdanswer-ai/danswerpkg:github/danswer-ai/danswerOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
European organizations using danswer-ai/danswer should immediately audit their deployment for this vulnerability and implement the following specific mitigations: 1) Enforce strict authorization checks on all file access endpoints, ensuring that the requesting user is the owner or has explicit permission to access the file identified by file_id. 2) Implement robust access control mechanisms such as role-based access control (RBAC) or attribute-based access control (ABAC) to limit file visibility. 3) Monitor and log all file access requests, especially those involving unusual file_id patterns or access attempts from unexpected users. 4) Conduct a thorough code review and penetration testing focused on IDOR and authorization bypass issues in the API. 5) If possible, isolate sensitive files or data in separate storage with additional access restrictions. 6) Educate developers and security teams on secure API design principles to prevent similar flaws. 7) Stay alert for official patches or updates from danswer-ai and apply them promptly once available. 8) Consider implementing Web Application Firewalls (WAF) with custom rules to detect and block suspicious file_id manipulation attempts until a patch is deployed.
Description
An 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.