CVE-2020-26312 GHSL-2020-254: Arbitrary file read and/or write in dotmesh
Attackers can read or write arbitrary files outside the target directory via malicious tarballs exploiting symbolic link handling in dotmesh.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2020-26312?
CVE-2020-26312 is a high-severity path traversal vulnerability in dotmesh-io dotmesh, published on 14 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
Dotmesh is a git-like command-line interface for capturing, organizing and sharing application states. In versions 0.8.1 and prior, the unsafe handling of symbolic links in an unpacking routine may enable attackers to read and/or write to arbitrary locations outside the designated target folder. The routine `untarFile` attempts to guard against creating symbolic links that point outside the directory a tar archive is extracted to. However, a malicious tarball first linking `subdir/parent` to `..` (allowed, because `subdir/..` falls within the archive root) and then linking `subdir/parent/escapes` to `..` results in a symbolic link pointing to the tarball’s parent directory, contrary to the routine’s goals. This issue may lead to arbitrary file write (with same permissions as the program running the unpack operation) if the attacker can control the archive file. Additionally, if the attacker has read access to the unpacked files, they may be able to read arbitrary system files the parent process has permissions to read. As of time of publication, no patch for this issue is available.
Which versions are affected by CVE-2020-26312?
3 open source packages ship an affected version, including github.com/dotmesh-io/dotmesh.
| Package | Affected | Fixed in |
|---|---|---|
github.com/dotmesh-io/dotmesh Go | All versions | None |
github.com/dotmesh-io/dotmesh Go | All versions to 0.8.1 | None |
github.com/dotmesh-io/dotmesh Go | All versions to 0.8.1 | None |
How do I fix CVE-2020-26312?
No fix has been published for CVE-2020-26312 yet. Limit exposure of the affected software until one is available.
Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.
Is CVE-2020-26312 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-26312 exists.
Sources
Also known as GHSA-hf54-fq2m-p9v6, GO-2024-2849.