# CVE-2019-10783: OS Command Injection in lsof

> The lsof npm module allows command injection via user input in exported methods, enabling arbitrary code execution.

- **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:** 29 Jan 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-whq6-mj2r-mjqc

## What is CVE-2019-10783?

CVE-2019-10783 is a critical command injection vulnerability in lsof, published on 29 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

All versions including 0.0.4 of lsof npm module are vulnerable to Command Injection. Every exported method used by the package uses the exec function to parse user input.

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

## Which versions are affected by CVE-2019-10783?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `lsof` | npm | All versions to 0.0.4 | None |
| `lsof` | npm | All versions to 0.0.4 | None |

Products: Isof Project Isof.

## How do I fix CVE-2019-10783?

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

## Is CVE-2019-10783 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-10783 and fix it if it is affected.

What it is: CVE-2019-10783 is a critical command injection vulnerability in lsof, published on 29 Jan 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-2019-10783 in the wild and no public exploit code.

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

## Sources

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

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