# CVE-2020-24654: Path traversal in n/a

> Attackers can use crafted TAR archives with symlinks to write files outside the extraction directory in KDE Ark.

- **Severity:** Low 3.3 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 2 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** CLEANSTART-2024-HZ44036, DEBIAN-CVE-2020-24654, DSA-4759-1, GHSA-wc24-5j7x-rp2x, MGASA-2020-0353, UBUNTU-CVE-2020-24654, USN-4482-1, openSUSE-SU-2020:1310-1, openSUSE-SU-2020:1310-2

## What is CVE-2020-24654?

CVE-2020-24654 is a low-severity path traversal vulnerability in Canonical Ubuntu Linux, published on 2 Sep 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

In KDE Ark before 20.08.1, a crafted TAR archive with symlinks can install files outside the extraction directory, as demonstrated by a write operation to a user's home directory.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

## Which versions are affected by CVE-2020-24654?

It affects 5 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ark` | SUSE:Package Hub 15 SP1 | All versions | 20.04.2-bp152.2.6.1 |
| `ark` | SUSE:Package Hub 15 SP1 | All versions | 20.04.2-bp152.2.6.1 |
| `ark` | SUSE:Package Hub 15 SP2 | All versions | 20.04.2-bp152.2.6.1 |
| `ark` | SUSE:Package Hub 15 SP2 | All versions | 20.04.2-bp152.2.6.1 |
| `ark` | openSUSE:Leap 15.1 | All versions | 20.04.2-bp152.2.6.1 |
| `ark` | openSUSE:Leap 15.1 | All versions | 20.04.2-bp152.2.6.1 |
| `ark` | openSUSE:Leap 15.2 | All versions | 20.04.2-bp152.2.6.1 |
| `ark` | openSUSE:Leap 15.2 | All versions | 20.04.2-bp152.2.6.1 |

Products: Canonical Ubuntu Linux, Debian Debian Linux, Fedoraproject Fedora, Kde Ark, Opensuse Leap.

## How do I fix CVE-2020-24654?

Upgrade to a fixed version.

## Is CVE-2020-24654 being exploited?

There is no known exploitation of CVE-2020-24654 in the wild and no public exploit code.

## Other vulnerabilities in Canonical Ubuntu Linux

- [CVE-2020-11651](https://insights.sbomify.com/CVE-2020-11651/): SaltStack Salt Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2020-7247](https://insights.sbomify.com/CVE-2020-7247/): OpenSMTPD Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2019-16928](https://insights.sbomify.com/CVE-2019-16928/): Exim Out-of-bounds Write (critical 9.8, exploited in the wild)
- [CVE-2018-6789](https://insights.sbomify.com/CVE-2018-6789/): Exim Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2015-2590](https://insights.sbomify.com/CVE-2015-2590/): Oracle Java SE and Java SE Embedded Remote Code Execution (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-24654 and fix it if it is affected.

What it is: CVE-2020-24654 is a low-severity path traversal vulnerability in Canonical Ubuntu Linux, published on 2 Sep 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-24654 in the wild and no public exploit code.

Affected product: Canonical Ubuntu Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-24654/ (Markdown: https://insights.sbomify.com/CVE-2020-24654/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-24654
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-24654
- OSV: https://osv.dev/vulnerability/CVE-2020-24654

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-24654/
Summaries are generated and may contain mistakes; the official description above is the record.