# CVE-2023-43207: Command injection in n/a

> Attackers can execute arbitrary commands on D-Link DWL-6610 devices via the configRestore parameter in the config upload handler.

- **Severity:** High 8.0 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Sep 2023
- **Updated:** 24 Sep 2024
- **Also known as:** GHSA-jhrc-rg5g-36c2

## What is CVE-2023-43207?

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

### Official description

D-LINK DWL-6610 FW_v_4.3.0.8B003C was discovered to contain a command injection vulnerability in the function config_upload_handler. This vulnerability allows attackers to execute arbitrary commands via the configRestore parameter.

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

## Which versions are affected by CVE-2023-43207?

It affects 1 product.


Products: Dlink Dwl-6610ap Firmware.

## How do I fix CVE-2023-43207?

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

## Is CVE-2023-43207 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-43202](https://insights.sbomify.com/CVE-2023-43202/): Command injection in n/a (high 8.0)
- [CVE-2023-43203](https://insights.sbomify.com/CVE-2023-43203/): Memory corruption in n/a (high 8.0)
- [CVE-2023-43204](https://insights.sbomify.com/CVE-2023-43204/): Command injection in n/a (high 8.0)
- [CVE-2023-43206](https://insights.sbomify.com/CVE-2023-43206/): Command injection in n/a (high 8.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-43207 and fix it if it is affected.

What it is: CVE-2023-43207 is a high-severity command injection vulnerability in n/a, published on 20 Sep 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-43207 in the wild and no public exploit code.

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-2023-43207/ (Markdown: https://insights.sbomify.com/CVE-2023-43207/index.md)
```

## Sources

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

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