# CVE-2018-10823: Command injection in n/a

> An authenticated attacker can execute arbitrary code on D-Link routers via command injection in the Sip parameter, gaining full device control.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Oct 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-qh9h-ccxh-x284

## What is CVE-2018-10823?

CVE-2018-10823 is a high-severity command injection vulnerability in n/a, published on 17 Oct 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered on D-Link DWR-116 through 1.06, DWR-512 through 2.02, DWR-712 through 2.02, DWR-912 through 2.02, DWR-921 through 2.02, and DWR-111 through 1.01 devices. An authenticated attacker may execute arbitrary code by injecting the shell command into the chkisg.htm page Sip parameter. This allows for full control over the device internals.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2018-10823?

It affects 4 products.


Products: Dlink Dwr-111 Firmware, Dlink Dwr-116 Firmware, Dlink Dwr-512 Firmware, Dlink Dwr-912 Firmware.

## How do I fix CVE-2018-10823?

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

## Is CVE-2018-10823 being exploited?

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

Public exploit code:

- D-Link Routers - Command Injection (exploitdb)
- D-Link Routers - Remote Command Injection (nuclei): http/cves/2018/CVE-2018-10823.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-10823 and fix it if it is affected.

What it is: CVE-2018-10823 is a high-severity command injection vulnerability in n/a, published on 17 Oct 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-10823 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-2018-10823/ (Markdown: https://insights.sbomify.com/CVE-2018-10823/index.md)
```

## Sources

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

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