What is CVE-2019-15599?

CVE-2019-15599 is a high-severity code injection vulnerability in tree-kill (npm), affecting versions < 1.2.2. It is fixed in 1.2.2. Untrusted input is evaluated as executable code within the application's runtime environment.

Which versions of tree-kill are affected by CVE-2019-15599?

tree-kill (npm) versions < 1.2.2 is affected.

Is there a fix for CVE-2019-15599?

Yes. CVE-2019-15599 is fixed in 1.2.2. Upgrade to this version or later.

Is CVE-2019-15599 exploitable, and should I be worried?

Whether CVE-2019-15599 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2019-15599 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2019-15599?

Upgrade tree-kill to 1.2.2 or later.

CVE-2019-15599 in tree-kill

Q: Which versions of tree-kill are affected by CVE-2019-15599?

tree-kill (npm) versions < 1.2.2 is affected.

Q: Is there a fix for CVE-2019-15599?

Yes. CVE-2019-15599 is fixed in 1.2.2. Upgrade to this version or later.

Q: Is CVE-2019-15599 exploitable, and should I be worried?

Whether CVE-2019-15599 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2019-15599 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2019-15599?

Upgrade tree-kill to 1.2.2 or later.

Summary

Command Injection in tree-kill

Versions of tree-kill prior to 1.2.2 are vulnerable to Command Injection. The package fails to sanitize values passed to the kill function. If this value is user-controlled it may allow attackers to run arbitrary commands in the server. The issue only affects Windows systems.

Impact

Untrusted input is evaluated as executable code within the application's runtime environment. Typical impact: arbitrary code execution within the application's privilege context.

Affected versions

tree-kill (< 1.2.2)

Security releases

tree-kill → 1.2.2 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade to version 1.2.2 or later.

Frequently Asked Questions

What is CVE-2019-15599? CVE-2019-15599 is a high-severity code injection vulnerability in tree-kill (npm), affecting versions < 1.2.2. It is fixed in 1.2.2. Untrusted input is evaluated as executable code within the application's runtime environment.
Which versions of tree-kill are affected by CVE-2019-15599? tree-kill (npm) versions < 1.2.2 is affected.
Is there a fix for CVE-2019-15599? Yes. CVE-2019-15599 is fixed in 1.2.2. Upgrade to this version or later.
Is CVE-2019-15599 exploitable, and should I be worried? Whether CVE-2019-15599 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2019-15599 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2019-15599? Upgrade tree-kill to 1.2.2 or later.

Other vulnerabilities in tree-kill

CVE-IDSeverityPackage summary

CVE-2019-15598Criticaltree-kill: Treekill Enables OS Command Injection