# CVE-2024-3799: Shell command injection in Phoniebox

> An attacker can execute arbitrary shell commands on Phoniebox devices by tricking a user into visiting a malicious website that sends crafted requests.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Jul 2024
- **Updated:** 28 Aug 2024
- **Also known as:** GHSA-98h6-g9rg-hxmr

## What is CVE-2024-3799?

CVE-2024-3799 is a high-severity command injection vulnerability in Phoniebox, published on 10 Jul 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Insecure handling of POST header parameter body included in requests being sent to an instance of the open-source project Phoniebox allows an attacker to create a website, which – when visited by a user – will send malicious requests to multiple hosts on the local network. If such a request reaches the server, it will cause a shell command execution.

This issue affects Phoniebox in all releases through 2.7. Newer 2.x releases were not tested, but they might also be vulnerable. 
Phoniebox in version 3.0 and higher are not affected.

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

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


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

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

## Is CVE-2024-3799 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-3799 is a high-severity command injection vulnerability in Phoniebox, published on 10 Jul 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-3799 in the wild and no public exploit code.

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

## Sources

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

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