aimhubio/aim: Path Traversal: '..filename'
CVE-2024-6396 is a critical-severity path traversal: '..filename' vulnerability in aimhubio/aim from Aimhubio, with a CVSS 3.0 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected aimhubio/aim versions: latest and earlier. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 53.1% chance of exploitation within 30 days, which is in the top 1% of all scored CVEs.
Exploitation in the next 30 days is more likely than not, according to EPSS.
What to do
- Check which version of aimhubio/aim 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 |
|---|---|---|---|
| Aimhubio | aimhubio/aim | latest and earlier | Not stated |
| Aimhubio | aim | 3.19.3 | 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
- HighData or code can be modified at will.
- 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:H/A:H. Scored by CNA (huntr.dev).
Official description
A vulnerability in the `_backup_run` function in aimhubio/aim version 3.19.3 allows remote attackers to overwrite any file on the host server and exfiltrate arbitrary data. The vulnerability arises due to improper handling of the `run_hash` and `repo.path` parameters, which can be manipulated to create and write to arbitrary file paths. This can lead to denial of service by overwriting critical system files, loss of private data, and potential remote code execution.
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: total).
- Record last changed materially (score, affected products, status or references).
References
Technical write-ups (may include proof of concept)
- huntr.com/bounties/c1b17afd-4656-47bb-8310-686a9e1b04a0Exploit, Third Party Advisory
Other vulnerabilities in aimhubio/aim
- 7.5 High severity
- 7.5 High severity
- 9.1 Critical severity
- 8.1 High severity
- 7.5 High severity
- 9.6 Critical severity
Recent Path Traversal: '..filename' vulnerabilities
- 9.1 Critical severity
- 7.3 High severity
- 9.8 Critical severity
- 7.2 High severity
- 7.5 High severity
- 7.5 High severity
Spotted an error? Tell us.