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

> Attackers can execute arbitrary commands remotely on D-Link routers via the version_upgrade.asp endpoint.

- **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:** 9 Sep 2024
- **Updated:** 9 Sep 2024
- **Also known as:** GHSA-726x-rvqx-m6j6

## What is CVE-2024-44335?

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

### Official description

D-Link DI-7003G v19.12.24A1, DI-7003GV2 v24.04.18D1, DI-7100G+V2 v24.04.18D1, DI-7100GV2 v24.04.18D1, DI-7200GV2 v24.04.18E1, DI-7300G+V2 v24.04.18D1, and DI-7400G+V2 v24.04.18D1 are vulnerable to Remote Command Execution (RCE) via version_upgrade.asp.

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

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


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

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

## Is CVE-2024-44335 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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