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

> An attacker can exploit a directory traversal vulnerability in GNOME file-roller to write files outside the intended extraction directory, potentially leading to code execution.

- **Severity:** Low 3.9 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 7 Apr 2021
- **Updated:** 4 Aug 2024
- **Also known as:** CLSA-2022-1643124469, DEBIAN-CVE-2020-36314, GHSA-xf7f-5p7r-xc3c, MGASA-2021-0311, RHSA-2021:4179, RLSA-2021:4179, SUSE-SU-2025:0032-1, UBUNTU-CVE-2020-36314, USN-4927-1

## What is CVE-2020-36314?

CVE-2020-36314 is a low-severity path traversal vulnerability in Fedoraproject Fedora, published on 7 Apr 2021. 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

fr-archive-libarchive.c in GNOME file-roller through 3.38.0, as used by GNOME Shell and other software, allows Directory Traversal during extraction because it lacks a check of whether a file's parent is a symlink in certain complex situations. NOTE: this issue exists because of an incomplete fix for CVE-2020-11736.

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

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

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `file-roller` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.28.1-4.el8 |
| `file-roller-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.28.1-4.el8 |
| `file-roller-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.28.1-4.el8 |
| `file-roller` | Rocky Linux:8 | All versions | 0:3.28.1-4.el8 |
| `file-roller` | SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | All versions | 3.20.3-15.9.1 |

Products: Fedoraproject Fedora, Gnome File-Roller.

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

Apply the vendor's patch.

## Is CVE-2020-36314 being exploited?

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

## Other vulnerabilities in Fedoraproject Fedora

- [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild)
- [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild)
- [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-36314 is a low-severity path traversal vulnerability in Fedoraproject Fedora, published on 7 Apr 2021. 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-36314 in the wild and no public exploit code.

Affected product: Fedoraproject Fedora. 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-36314/ (Markdown: https://insights.sbomify.com/CVE-2020-36314/index.md)
```

## Sources

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

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