# CVE-2019-15599: Command Injection in tree-kill

> Attackers can execute arbitrary code on Windows systems by controlling input to the tree-kill library, requiring an upgrade to mitigate.

- **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:** Yes
- **Published:** 18 Dec 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-884p-74jh-xrg2

## What is CVE-2019-15599?

CVE-2019-15599 is a critical code injection vulnerability in tree-kill, published on 18 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A Code Injection exists in tree-kill on Windows which allows a remote code execution when an attacker is able to control the input into the command.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `tree-kill` | npm | All versions | 1.2.2 |
| `tree-kill` | npm | All versions | 1.2.2 |

Products: Tree-Kill Project Tree-Kill.

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

Upgrade tree-kill to 1.2.2 or later.

## Is CVE-2019-15599 being exploited?

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

## Other vulnerabilities in tree-kill

- [CVE-2019-15598](https://insights.sbomify.com/CVE-2019-15598/): Treekill Enables OS Command Injection (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-15599 is a critical code injection vulnerability in tree-kill, published on 18 Dec 2019. 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-15599 in the wild and no public exploit code.

Affected packages and fixed versions:
- tree-kill (npm): affected all versions; fixed in 1.2.2
- tree-kill (npm): affected all versions; fixed in 1.2.2

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-15599/ (Markdown: https://insights.sbomify.com/CVE-2019-15599/index.md)
```

## Sources

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

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