CVE-2020-7628: Command Injection in umount

umount Updated 02 Oct 2025

Summary

10/06/2020
No i
Critical
9.8

CVE-2020-7628: Command Injection in umount. Affects umount versions < 1.1.6. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The umount package is an npm package used for unmounting file systems in Unix-like operating systems. It provides a command-line interface for unmounting mounted devices. The package is vulnerable to command injection, where user-controlled input is not properly sanitized and is directly passed to an exec call on the umount function. This allows attackers to execute arbitrary code on the system if they can control the device value passed to the function.

Vulnerability Detail

The vulnerability in the umount package arises from the lack of input sanitization. When a user-controlled device value is passed to the umount function, it is not properly validated, allowing an attacker to inject malicious commands. This can lead to arbitrary code execution with the privileges of the user running the umount command. The impact of this vulnerability is critical, as it allows an attacker to gain unauthorized access and potentially compromise the entire system.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As there is no fix available, the best workaround is to use an alternative package that is not vulnerable to command injection. This will help mitigate the risk of arbitrary code execution. It is important to regularly check for updates and patches for the umount package to ensure the vulnerability is addressed once a fix is released.

Conclusion

The umount package is vulnerable to command injection, allowing attackers to execute arbitrary code on the system. Currently, no fix is available, so it is recommended to use an alternative package until a fix is released. Regularly check for updates and patches to ensure the vulnerability is addressed. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for umount →

Share this vulnerability

FAQ

The impact of this vulnerability is critical, as it allows an attacker to execute arbitrary code on the system with the privileges of the user running the umount command. This can lead to unauthorized access and potential compromise of the entire system.

No, currently there is no fix available for this vulnerability. It is recommended to use an alternative package until a fix is released.

To mitigate the risk of this vulnerability, it is recommended to use an alternative package that is not vulnerable to command injection. Regularly check for updates and patches for the umount package to ensure the vulnerability is addressed once a fix is released.

You can find more information about this vulnerability in the official advisory or the GitHub repository for the umount package.

Yes, the CVSS score for this vulnerability is 9.8, indicating its critical severity.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback