# CVE-2024-43804: OS Command Injection via Port Scan Functionality in Roxy-WI

> Authenticated attackers can execute arbitrary OS commands on the server via the port scan feature due to unsanitized input in subprocess calls.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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:** 29 Aug 2024
- **Updated:** 29 Aug 2024
- **Also known as:** GHSA-qc52-vwwj-5585

## What is CVE-2024-43804?

CVE-2024-43804 is a high-severity command injection vulnerability in roxy-wi, published on 29 Aug 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Roxy-WI is a web interface for managing Haproxy, Nginx, Apache and Keepalived servers. An OS Command Injection vulnerability allows any authenticated user on the application to execute arbitrary code on the web application server via port scanning functionality. User-supplied input is used without validation when constructing and executing an OS command. User supplied JSON POST data is parsed and if "id" JSON key does not exist, JSON value supplied via "ip" JSON key is assigned to the "ip" variable. Later on, "ip" variable which can be controlled by the attacker is used when constructing the cmd and cmd1 strings without any extra validation. Then, server_mod.subprocess_execute function is called on both cmd1 and cmd2. When the definition of the server_mod.subprocess_execute() function is analyzed, it can be seen that subprocess.Popen() is called on the input parameter with shell=True which results in OS Command Injection. This issue has not yet been patched. Users are advised to contact the Roxy-WI to coordinate a fix.

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

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

It affects 1 product.


Products: Roxy-Wi Roxy-Wi.

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

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

## Is CVE-2024-43804 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-43804 exists.

## Other vulnerabilities in roxy-wi

- [CVE-2022-31161](https://insights.sbomify.com/CVE-2022-31161/): Roxy-WI Vulnerable to Unauthenticated Remote Code Execution via ssl_cert Upload (critical 10.0)
- [CVE-2022-31137](https://insights.sbomify.com/CVE-2022-31137/): Unauthenticated Remote Code Execution in Roxy-WI (critical 10.0)
- [CVE-2022-31125](https://insights.sbomify.com/CVE-2022-31125/): Authentication Bypass in Roxy-wi (critical 10.0)
- [CVE-2022-31126](https://insights.sbomify.com/CVE-2022-31126/): Unauthenticated Remote Code Execution in Roxy-wi (critical 10.0)
- [CVE-2021-38167](https://insights.sbomify.com/CVE-2021-38167/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-43804 is a high-severity command injection vulnerability in roxy-wi, published on 29 Aug 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-43804 exists.

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

## Sources

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

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