# CVE-2024-51115: Command injection in n/a

> Attackers can execute arbitrary commands on the DCME-320 device due to a command injection vulnerability.

- **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:** 5 Nov 2024
- **Updated:** 6 Nov 2024
- **Also known as:** GHSA-q5mq-2xwr-j447

## What is CVE-2024-51115?

CVE-2024-51115 is a critical command injection vulnerability in n/a, published on 5 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

DCME-320 v7.4.12.90 was discovered to contain a command injection vulnerability.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

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

It affects 1 product.


Products: Dcnetworks Dcme-320 Firmware.

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

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

## Is CVE-2024-51115 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2026-2000](https://insights.sbomify.com/CVE-2026-2000/): DCN DCME-320 Web Management Backend bridge_cfg.php apply_config command injection (medium 5.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-51115 is a critical command injection vulnerability in n/a, published on 5 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-51115 exists.

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

## Sources

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

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