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

> Attackers can execute arbitrary commands via the path parameter in the upgrade_filter.asp file of the DI_8200 device.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Oct 2024
- **Updated:** 15 Oct 2024
- **Also known as:** GHSA-2988-8m49-6wmh

## What is CVE-2024-44413?

CVE-2024-44413 is a high-severity command injection vulnerability in n/a, published on 11 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was discovered in DI_8200-16.07.26A1, which has been classified as critical. This issue affects the upgrade_filter_asp function in the upgrade_filter.asp file. Manipulation of the path parameter can lead to command injection.

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

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


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

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

## Is CVE-2024-44413 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-44413 is a high-severity command injection vulnerability in n/a, published on 11 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-44413 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-44413/ (Markdown: https://insights.sbomify.com/CVE-2024-44413/index.md)
```

## Sources

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

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