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

> Remote attackers can execute arbitrary commands on the Eir D1000 modem via the TR-064 protocol due to improper access restrictions.

- **Severity:** Critical 9.8 (`CVSS:3.0/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:** 16 May 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-84jm-8434-c983

## What is CVE-2016-10372?

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

### Official description

The Eir D1000 modem does not properly restrict the TR-064 protocol, which allows remote attackers to execute arbitrary commands via TCP port 7547, as demonstrated by opening WAN access to TCP port 80, retrieving the login password (which defaults to the Wi-Fi password), and using the NewNTPServer feature.

Weakness: CWE-264

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

It affects 1 product.


Products: Eir D1000 Modem Firmware.

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

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

## Is CVE-2016-10372 being exploited?

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

Public exploit code:

- Zyxel/Eir D1000 DSL Modem NewNTPServer Command Injection Over TR-064 (metasploit)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-10372 is a critical command injection vulnerability in n/a, published on 16 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-10372 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-2016-10372/ (Markdown: https://insights.sbomify.com/CVE-2016-10372/index.md)
```

## Sources

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

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