CVE-2020-7628
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedumount through 1.1.6 is vulnerable to Command Injection. The argument device can be controlled by users without any sanitization.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceumount version 1.1.6 and earlier contains a command injection vulnerability where the device argument is not sanitized before being passed to the underlying system command, allowing an attacker to inject arbitrary shell commands.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versions<= 1.1.6CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify umount package installationRun 'npm list umount' or check package.json dependencies to see if the umount package is installedAffected if umount package is listed with version 1.1.6 or earlier, or no version specified (implying latest which may be vulnerable)
-
Verify package versionRun 'npm list umount --depth=0' or inspect node_modules/umount/package.json to find the exact installed versionAffected if Version is 1.1.6 or lower, or the version field is missing/undefined in package.json
-
Trace device argument sourceSearch codebase for calls to umount() function and inspect where the device argument originates (e.g., user input, file, API parameter)Affected if The device argument is sourced from untrusted input such as HTTP request parameters, user-provided files, or command-line arguments without sanitization
-
Check for command injection vectorsReview the umount function call in your code: look for string concatenation or template literals building the device argument, or direct passage of variables to the device parameterAffected if The device parameter accepts raw string input that could contain shell metacharacters (semicolons, pipes, backticks, $()) without validation
You are affected if the umount npm package version 1.1.6 or earlier is installed AND user-controlled input flows to the device argument without sanitization.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade to a patched version of umount and implement strict input validation on the device argument to prevent command injection. If no patched version exists, avoid passing untrusted input to the device parameter.
umount version > 1.1.6 (latest version)
- Run 'npm install umount@latest' or 'npm install umount@>1.1.6' to upgrade to a fixed version
- Verify the upgrade by checking the installed version with 'npm list umount'
- Test that your application still functions correctly after the upgrade
- If using in code, ensure any device arguments are properly validated before passing to umount functions
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-7628 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-7628 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data