# CVE-2024-8684: OS Command Injection vulnerability in Revolution Pi

> An authenticated attacker can execute arbitrary OS commands on Revolution Pi devices via a vulnerable PHP endpoint.

- **Severity:** High 8.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Feb 2025
- **Updated:** 12 Feb 2025
- **Also known as:** GHSA-6w6c-5vv5-gw2w

## What is CVE-2024-8684?

CVE-2024-8684 is a high-severity command injection vulnerability in KUNBUS GmbH Revolution Pi, published on 10 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

OS Command Injection vulnerability in Revolution Pi version 2022-07-28-revpi-buster from KUNBUS GmbH. This vulnerability could allow an authenticated attacker to execute OS commands on the device via the ‘php/dal.php’ endpoint, in the ‘arrSaveConfig’ parameter.

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

## Which versions are affected by CVE-2024-8684?


## How do I fix CVE-2024-8684?

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

## Is CVE-2024-8684 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-8684 and fix it if it is affected.

What it is: CVE-2024-8684 is a high-severity command injection vulnerability in KUNBUS GmbH Revolution Pi, published on 10 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-8684 in the wild and no public exploit code.

Affected product: KUNBUS GmbH Revolution Pi. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2024-8684/ (Markdown: https://insights.sbomify.com/CVE-2024-8684/index.md)
```

## Sources

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

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