stitionai/devika: External Control of File Name or Path
CVE-2024-5334 is a high-severity external control of file name or path vulnerability in stitionai/devika from Stitionai, with a CVSS 3.0 base score of 7.5 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 2.07% chance of exploitation within 30 days, higher than 82% of scored CVEs.
High severity with no evidence of exploitation so far.
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
- NoneAvailability is not affected.
Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. Scored by CNA (huntr.dev).
Official description
A local file read vulnerability exists in the stitionai/devika repository, affecting the latest version. The vulnerability is due to improper handling of the 'snapshot_path' parameter in the '/api/get-browser-snapshot' endpoint. An attacker can exploit this vulnerability by crafting a request with a malicious 'snapshot_path' parameter, leading to arbitrary file read from the system. This issue impacts the security of the application by allowing unauthorized access to sensitive files on the server.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: External Control of File Name or Path
The product allows user input to control or influence paths or file names that are used in filesystem operations.
How developers prevent this class of flaw
- When the set of filenames is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames, and reject all other inputs. For example, ID 1 could map to inbox.txt and ID 2 could map to profile.txt. Features such as the ESAPI AccessReferenceMap provide this capability.
- Run your code in a jail or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict all access to files within a particular directory. Examples include the Unix chroot jail and AppArmor. In general, managed code may provide some protection. This may not be a feasible solution, and it only limits the impact to the operating system; the rest of your application may still be subject to compromise. Be careful to avoid CWE-243 and other weaknesses related to jails.
- For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
More External Control of File Name or Path vulnerabilities (CWE-73)
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
Patches and release notes
Technical write-ups (may include proof of concept)
- huntr.com/bounties/7eec128b-1bf5-4922-a95c-551ad3695cf6Exploit, Third Party Advisory
Other vulnerabilities in stitionai/devika
- 9.1 Critical severity
- 7.5 High severity
- 8.1 High severity
- 9.1 Critical severity
- 8.1 High severity
- 8.8 High severity
Recent External Control of File Name or Path vulnerabilities
- 7.2 High severity
- 8.1 High severity
- 8.8 High severity
- 7.1 High severity
- 7.8 High severity
- 7.5 High severity
Spotted an error? Tell us.