stitionai/devika: Path Traversal: '..filename'
CVE-2024-5926 is a critical-severity path traversal: '..filename' vulnerability in stitionai/devika from Stitionai, with a CVSS 3.0 base score of 9.1 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. There is no confirmed exploitation so far. EPSS estimates a 0.86% chance of exploitation within 30 days, higher than 59% of scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Check which version of stitionai/devika you run against the affected versions below, and install the vendor's latest release.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Stitionai | stitionai/devika | Not specified in the record | Not stated |
| Stitionai | devika | all versions | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- NoneNothing can be modified.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H. Scored by CNA (huntr.dev).
Official description
A path traversal vulnerability in the get-project-files functionality of stitionai/devika allows attackers to read arbitrary files from the filesystem and cause a Denial of Service (DoS). This issue is present in all versions of the application. The vulnerability arises due to insufficient path sanitization for the 'project-name' parameter, enabling attackers to specify paths that traverse the filesystem. By setting 'project-name' to the root directory, an attacker can cause the application to attempt to read the entire filesystem, leading to a DoS condition.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Path Traversal: '..filename'
The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize '..filename' (leading backslash dot dot) sequences that can resolve to a location that is outside of that directory.
How developers prevent this class of flaw
- Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Technical write-ups (may include proof of concept)
- huntr.com/bounties/19af24fe-9b90-4638-8fbc-b18def6985d7Exploit, Third Party Advisory
Other vulnerabilities in stitionai/devika
- 9.1 Critical severity
- 7.5 High severity
- 8.1 High severity
- 8.1 High severity
- 8.8 High severity
- 7.5 High severity
Recent Path Traversal: '..filename' vulnerabilities
- 7.3 High severity
- 9.8 Critical severity
- 7.2 High severity
- 7.5 High severity
- 7.5 High severity
- 8.4 High severity
Spotted an error? Tell us.