# CVE-2020-7775: Command Injection

> Attackers can execute arbitrary commands via improper neutralization of arguments in the freediskspace npm package.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Feb 2021
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-4gfq-6m28-m5mg

## What is CVE-2020-7775?

CVE-2020-7775 is a critical command injection vulnerability in freediskspace, published on 2 Feb 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

This affects all versions of package freediskspace. The vulnerability arises out of improper neutralization of arguments in line 71 of freediskspace.js.

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

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

2 open source packages ship an affected version, including freediskspace. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `freediskspace` | npm | All versions to 1.2.0 | None |
| `freediskspace` | npm | All versions to 1.2.0 | None |

Products: Freediskspace Project Freediskproject.

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

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

## Is CVE-2020-7775 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-7775 is a critical command injection vulnerability in freediskspace, published on 2 Feb 2021. 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-7775 in the wild and no public exploit code.

Affected packages and fixed versions:
- freediskspace (npm): affected all versions up to 1.2.0; no fix listed
- freediskspace (npm): affected all versions up to 1.2.0; 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-7775/ (Markdown: https://insights.sbomify.com/CVE-2020-7775/index.md)
```

## Sources

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

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