# GHSA-wqhw-frpx-5mmp: Command Injection in tomato

> Attackers can execute arbitrary system commands via the /api/exec endpoint due to lack of input validation in the tomato library.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Sep 2020

## What is GHSA-wqhw-frpx-5mmp?

GHSA-wqhw-frpx-5mmp is a command injection vulnerability in tomato, published on 2 Sep 2020. It can be exploited over the network, with no action from the victim.

### Official description

All versions of `tomato` are vulnerable to Command Injection. The /api/exec endpoint does not validate user input allowing attackers to run arbitrary commands in the system.

## Recommendation

No fix is currently available. Consider using an alternative module until a fix is made available.

## Which versions are affected by GHSA-wqhw-frpx-5mmp?

2 open source packages ship an affected version, including tomato.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `tomato` | npm | All versions | None |
| `tomato` | npm | All versions | None |

## How do I fix GHSA-wqhw-frpx-5mmp?

No fix has been published for GHSA-wqhw-frpx-5mmp yet. Limit exposure of the affected software until one is available.

## Is GHSA-wqhw-frpx-5mmp being exploited?

There is no known exploitation of GHSA-wqhw-frpx-5mmp in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-wqhw-frpx-5mmp and fix it if it is affected.

What it is: GHSA-wqhw-frpx-5mmp is a command injection vulnerability in tomato, published on 2 Sep 2020. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-wqhw-frpx-5mmp in the wild and no public exploit code.

Affected packages and fixed versions:
- tomato (npm): affected all versions; no fix listed
- tomato (npm): affected all versions; 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/GHSA-wqhw-frpx-5mmp/ (Markdown: https://insights.sbomify.com/GHSA-wqhw-frpx-5mmp/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-wqhw-frpx-5mmp

---
From sbomify Insights: https://insights.sbomify.com/GHSA-wqhw-frpx-5mmp/
Summaries are generated and may contain mistakes; the official description above is the record.