# CVE-2022-25973: Arbitrary Command Execution

> Attackers can execute arbitrary commands via the kill function due to missing sanitization of the port argument in the mc-kill-port npm package.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Aug 2022
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-2cg4-7q4x-7rr2

## What is CVE-2022-25973?

CVE-2022-25973 is a high-severity command injection vulnerability in mc-kill-port, published on 10 Aug 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

All versions of package mc-kill-port are vulnerable to Arbitrary Command Execution via the kill function, due to missing sanitization of the port argument.

Weakness: CWE-88 (Improper Neutralization of Argument Delimiters in a Command)

## Which versions are affected by CVE-2022-25973?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mc-kill-port` | npm | All versions to 1.0.1 | None |
| `mc-kill-port` | npm | All versions to 1.0.1 | None |

Products: Mc-Kill-Port Project Mc-Kill-Port.

## How do I fix CVE-2022-25973?

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

## Is CVE-2022-25973 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-25973 and fix it if it is affected.

What it is: CVE-2022-25973 is a high-severity command injection vulnerability in mc-kill-port, published on 10 Aug 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-25973 in the wild and no public exploit code.

Affected packages and fixed versions:
- mc-kill-port (npm): affected all versions up to 1.0.1; no fix listed
- mc-kill-port (npm): affected all versions up to 1.0.1; 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-2022-25973/ (Markdown: https://insights.sbomify.com/CVE-2022-25973/index.md)
```

## Sources

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

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