# CVE-2019-10796: OS Command Injection in rpi

> The rpi library allows arbitrary command execution via unsanitized input in the GPIO function, requiring an upgrade to secure Node.js applications.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Feb 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-vf26-7gjf-f92r

## What is CVE-2019-10796?

CVE-2019-10796 is a critical command injection vulnerability in rpi, published on 24 Feb 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

rpi through 0.0.3 allows execution of arbritary commands. The variable pinNumbver in function GPIO within src/lib/gpio.js is used as part of the arguement of exec function without any sanitization.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2019-10796?

2 open source packages ship an affected version, including rpi. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `rpi` | npm | All versions to 0.0.3 | None |
| `rpi` | npm | All versions to 0.0.3 | None |

Products: Rpi Project Rpi.

## How do I fix CVE-2019-10796?

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

## Is CVE-2019-10796 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-10796 and fix it if it is affected.

What it is: CVE-2019-10796 is a critical command injection vulnerability in rpi, published on 24 Feb 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 CVE-2019-10796 in the wild and no public exploit code.

Affected packages and fixed versions:
- rpi (npm): affected all versions up to 0.0.3; no fix listed
- rpi (npm): affected all versions up to 0.0.3; 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-2019-10796/ (Markdown: https://insights.sbomify.com/CVE-2019-10796/index.md)
```

## Sources

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

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