# CVE-2016-10178: Command injection in n/a

> An attacker can execute arbitrary commands with root privileges on the D-Link DWR-932B router by sending a specific UDP packet to port 39889.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jan 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-jjh8-q2f2-rvgj

## What is CVE-2016-10178?

CVE-2016-10178 is a critical command injection vulnerability in n/a, published on 30 Jan 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered on the D-Link DWR-932B router. HELODBG on port 39889 (UDP) launches the "/sbin/telnetd -l /bin/sh" command.

Weakness: CWE-254

## Which versions are affected by CVE-2016-10178?

It affects 1 product.


Products: Dlink Dwr-932b Firmware.

## How do I fix CVE-2016-10178?

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

## Is CVE-2016-10178 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-10177](https://insights.sbomify.com/CVE-2016-10177/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2016-10182](https://insights.sbomify.com/CVE-2016-10182/): Command injection in n/a (critical 9.8)
- [CVE-2016-10179](https://insights.sbomify.com/CVE-2016-10179/): Hardcoded credentials in n/a (high 7.5)
- [CVE-2016-10180](https://insights.sbomify.com/CVE-2016-10180/): Weak cryptography in n/a (high 7.5)
- [CVE-2016-10181](https://insights.sbomify.com/CVE-2016-10181/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-10178 and fix it if it is affected.

What it is: CVE-2016-10178 is a critical command injection vulnerability in n/a, published on 30 Jan 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-10178 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-2016-10178/ (Markdown: https://insights.sbomify.com/CVE-2016-10178/index.md)
```

## Sources

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

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