# GHSA-9wjh-jr2j-6r4x: Remote Code Execution in pi_video_recording

> Attackers can execute arbitrary commands via the /api/record/start endpoint due to insufficient input validation in the pi_video_recording library.

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

## What is GHSA-9wjh-jr2j-6r4x?

GHSA-9wjh-jr2j-6r4x is a command injection vulnerability in pi_video_recording, published on 2 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

All versions of `pi_video_recording` are vulnerable to Remote Code Execution. Due to insufficient input validation the server executes arbitrary code through the /api/record/start endpoint.  After running the server, `curl -POST -H "Content-Type: application/json" -d '{"filename": " || touch /tmp/worked;"}' http://localhost:5000/api/record/start`creates a file in the /tmp/ directory

## Recommendation

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

## Which versions are affected by GHSA-9wjh-jr2j-6r4x?

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


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

## How do I fix GHSA-9wjh-jr2j-6r4x?

No fix has been published for GHSA-9wjh-jr2j-6r4x yet. Limit exposure of the affected software until one is available.

## Is GHSA-9wjh-jr2j-6r4x being exploited?

There is no known exploitation of GHSA-9wjh-jr2j-6r4x in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-9wjh-jr2j-6r4x and fix it if it is affected.

What it is: GHSA-9wjh-jr2j-6r4x is a command injection vulnerability in pi_video_recording, published on 2 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-9wjh-jr2j-6r4x in the wild and no public exploit code.

Affected packages and fixed versions:
- pi_video_recording (npm): affected all versions; no fix listed
- pi_video_recording (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-9wjh-jr2j-6r4x/ (Markdown: https://insights.sbomify.com/GHSA-9wjh-jr2j-6r4x/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-9wjh-jr2j-6r4x

---
From sbomify Insights: https://insights.sbomify.com/GHSA-9wjh-jr2j-6r4x/
Summaries are generated and may contain mistakes; the official description above is the record.