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

> Attackers can execute arbitrary commands on D-Link DI_8004W routers via the jhttpd msp_info_htm function.

- **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:** 23 Aug 2024
- **Updated:** 23 Aug 2024
- **Also known as:** GHSA-723q-4x66-vrf2

## What is CVE-2024-44381?

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

### Official description

D-Link DI_8004W 16.07.26A1 contains a command execution vulnerability in jhttpd msp_info_htm function.

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

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

It affects 1 product.


Products: Dlink Di 8004w Firmware.

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

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

## Is CVE-2024-44381 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-44382](https://insights.sbomify.com/CVE-2024-44382/): Command injection in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-44381 is a high-severity command injection vulnerability in n/a, published on 23 Aug 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-44381 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-44381/ (Markdown: https://insights.sbomify.com/CVE-2024-44381/index.md)
```

## Sources

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

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