# CVE-2019-10220: Path traversal in kernel:

> Attackers can inject relative paths in CIFS directory entries, potentially reading or modifying files outside intended directories.

- **Severity:** High 8.0 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 27 Nov 2019
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2019-10220, GHSA-539c-rp35-q667, SUSE-SU-2019:3019-1, SUSE-SU-2019:3216-1, SUSE-SU-2019:3255-1, UBUNTU-CVE-2019-10220

## What is CVE-2019-10220?

CVE-2019-10220 is a high-severity path traversal vulnerability in Canonical Ubuntu Linux, published on 27 Nov 2019. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Linux kernel CIFS implementation, version 4.9.0 is vulnerable to a relative paths injection in directory entry lists.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2019-10220?

It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `kgraft-patch-SLE12-SP4_Update_8` | SUSE:Linux Enterprise Live Patching 12 SP4 | All versions | 3-2.1 |
| `kgraft-patch-SLE12-SP4_Update_9` | SUSE:Linux Enterprise Live Patching 12 SP4 | All versions | 2-2.1 |
| `kernel-livepatch-SLE15_Update_14` | SUSE:Linux Enterprise Live Patching 15 | All versions | 3-2.1 |
| `kernel-livepatch-SLE15_Update_15` | SUSE:Linux Enterprise Live Patching 15 | All versions | 3-2.1 |
| `kernel-livepatch-SLE15-SP1_Update_5` | SUSE:Linux Enterprise Live Patching 15 SP1 | All versions | 3-2.1 |
| `kernel-livepatch-SLE15-SP1_Update_6` | SUSE:Linux Enterprise Live Patching 15 SP1 | All versions | 3-2.1 |

Products: Canonical Ubuntu Linux, Debian Debian Linux, Linux kernel.

## How do I fix CVE-2019-10220?

Apply the vendor's patch.

## Is CVE-2019-10220 being exploited?

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

Public exploit code:

- https://github.com/Trinadh465/linux-3.0.35_CVE-2019-10220 (github_poc): https://github.com/Trinadh465/linux-3.0.35_CVE-2019-10220

## 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-2019-10220 and fix it if it is affected.

What it is: CVE-2019-10220 is a high-severity path traversal vulnerability in Canonical Ubuntu Linux, published on 27 Nov 2019. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-10220 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-2019-10220/ (Markdown: https://insights.sbomify.com/CVE-2019-10220/index.md)
```

## Sources

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

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