# CVE-2019-10786: Improper Input Validation in network-manager

> Remote attackers can execute arbitrary commands via the execSync argument in the network-manager npm library.

- **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:** 4 Feb 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-ph32-23p8-9rw5

## What is CVE-2019-10786?

CVE-2019-10786 is a critical command injection vulnerability in network-manager, published on 4 Feb 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

network-manager through 1.0.2 allows remote attackers to execute arbitrary commands via the "execSync()" argument.

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

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

2 open source packages ship an affected version, including network-manager. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `network-manager` | npm | All versions to 1.0.2 | None |
| `network-manager` | npm | All versions to 1.0.2 | None |

Products: Network-Manager Project Network-Manager.

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

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

## Is CVE-2019-10786 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-10786 is a critical command injection vulnerability in network-manager, published on 4 Feb 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-10786 in the wild and no public exploit code.

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

## Sources

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

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