# CVE-2020-7628: Command Injection in umount

> The umount library allows command injection via unsanitized device arguments, enabling attackers to execute arbitrary commands.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Apr 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-6q48-vjq2-mwcj

## What is CVE-2020-7628?

CVE-2020-7628 is a critical command injection vulnerability in install-package, published on 2 Apr 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

umount through 1.1.6 is vulnerable to Command Injection. The argument device can be controlled by users without any sanitization.

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

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

2 open source packages ship an affected version, including umount. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `umount` | npm | All versions to 1.1.6 | None |
| `umount` | npm | All versions to 1.1.6 | None |

Products: Install-Package Project Install-Package, Umount Project Umount.

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

No fix has been published for CVE-2020-7628 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-7628 being exploited?

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

## Other vulnerabilities in install-package

- [CVE-2020-7629](https://insights.sbomify.com/CVE-2020-7629/): OS Command Injection in install-package (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-7628 is a critical command injection vulnerability in install-package, published on 2 Apr 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-7628 in the wild and no public exploit code.

Affected packages and fixed versions:
- umount (npm): affected all versions up to 1.1.6; no fix listed
- umount (npm): affected all versions up to 1.1.6; no fix listed

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-7628/ (Markdown: https://insights.sbomify.com/CVE-2020-7628/index.md)
```

## Sources

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

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