CVE-2020-7775
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 · uneditedThis affects all versions of package freediskspace. The vulnerability arises out of improper neutralization of arguments in line 71 of freediskspace.js.
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 · moderate confidenceThe freediskspace npm package (all versions) contains a command injection vulnerability due to improper neutralization of arguments in the disk space checking logic at line 71 of freediskspace.js. An attacker can exploit this by providing malicious arguments, potentially allowing arbitrary command execution on the host system.
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 versionsCVSS 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.
-
Verify freediskspace package presenceSearch for 'freediskspace' in your project's package.json under dependencies or devDependencies, or check if it exists in node_modules/freediskspaceAffected if The package is listed in dependencies or node_modules/freediskspace exists
-
Confirm package versionRun 'npm list freediskspace' or check node_modules/freediskspace/package.json to identify the installed versionAffected if Any version is installed (all versions are affected)
-
Identify call sites in your codeSearch your codebase for imports or requires of freediskspace (e.g., 'require("freediskspace")' or 'import ... from "freediskspace"') and identify where the function is invokedAffected if The freediskspace function is called with arguments in your application
-
Check argument source for user controlReview the code paths leading to freediskspace calls; determine if any arguments (such as drive letters or paths) originate from user input, request parameters, environment variables, or external APIsAffected if Arguments passed to freediskspace can be influenced by untrusted input
-
Inspect the vulnerable source if accessibleExamine line 71 of node_modules/freediskspace/freediskspace.js to confirm the command construction uses unsanitized inputAffected if The code at line 71 directly concatenates arguments into a shell command without validation
Your environment is affected if the freediskspace npm package is installed and any user-controlled or untrusted input can reach its function arguments, enabling command injection.
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.
From vendor dataReplace the freediskspace package with a secure alternative or implement disk space checking using native Node.js APIs (e.g., child_process with built-in commands using fixed arguments, or platform-specific modules). Review all call sites to ensure no user-controlled input reaches the vulnerable function.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-7775 — 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-7775 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