# CVE-2024-29167: Command injection in SVR-116

> Remote authenticated administrators can execute arbitrary OS commands on SEEnergy SVR-116 devices via crafted requests.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Apr 2024
- **Updated:** 12 Aug 2024
- **Also known as:** GHSA-mjcw-8498-wxpx

## What is CVE-2024-29167?

CVE-2024-29167 is a high-severity command injection vulnerability in SEEnergy Corp. SVR-116, published on 4 Apr 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

SVR-116 firmware version 1.6.0.30028871 allows a remote authenticated attacker with an administrative privilege to execute arbitrary OS commands by sending a specially crafted request to the product.

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

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


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

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

## Is CVE-2024-29167 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-29167 is a high-severity command injection vulnerability in SEEnergy Corp. SVR-116, published on 4 Apr 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-29167 in the wild and no public exploit code.

Affected product: SEEnergy Corp. SVR-116. 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-29167/ (Markdown: https://insights.sbomify.com/CVE-2024-29167/index.md)
```

## Sources

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

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