# CVE-2020-14342: Command injection in cifs-utils

> An attacker with sudo access to mount.cifs can inject arbitrary commands via the Samba password prompt, leading to privilege escalation.

- **Severity:** Medium 4.4 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** ALPINE-CVE-2020-14342, AZL-6353, DEBIAN-CVE-2020-14342, GHSA-7mmj-72wg-6gpv, MGASA-2020-0376, SUSE-SU-2020:2728-1, SUSE-SU-2020:2729-1, UBUNTU-CVE-2020-14342, openSUSE-SU-2020:1579-1

## What is CVE-2020-14342?

CVE-2020-14342 is a medium-severity command injection vulnerability in Fedoraproject Fedora, published on 9 Sep 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

It was found that cifs-utils' mount.cifs was invoking a shell when requesting the Samba password, which could be used to inject arbitrary commands. An attacker able to invoke mount.cifs with special permission, such as via sudo rules, could use this flaw to escalate their privileges.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command), CWE-77 (Improper Neutralization of Special Elements used in a Command)

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

It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `cifs-utils` | SUSE:Linux Enterprise Module for Basesystem 15 SP1 | All versions | 6.9-5.6.1 |
| `cifs-utils` | SUSE:Linux Enterprise Module for Basesystem 15 SP2 | All versions | 6.9-5.6.1 |
| `cifs-utils` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 6.9-13.11.1 |
| `cifs-utils` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 6.9-13.11.1 |
| `cifs-utils` | SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 6.9-13.11.1 |
| `cifs-utils` | openSUSE:Leap 15.1 | All versions | 6.9-lp151.4.7.1 |

Products: Fedoraproject Fedora, Opensuse Leap, Samba Cifs-Utils.

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

Apply the vendor's patch.

## Is CVE-2020-14342 being exploited?

There is no known exploitation of CVE-2020-14342 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-14342 and fix it if it is affected.

What it is: CVE-2020-14342 is a medium-severity command injection vulnerability in Fedoraproject Fedora, published on 9 Sep 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-14342 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-14342/ (Markdown: https://insights.sbomify.com/CVE-2020-14342/index.md)
```

## Sources

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

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