# CVE-2015-1187: D-Link and TRENDnet Multiple Devices Remote Code Execution

> Remote attackers can execute arbitrary code on D-Link and TRENDnet devices via the ping utility's address parameter.

- **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:** Yes, since 25 Mar 2022 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Sep 2017
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-2cvq-m957-r86c

## What is CVE-2015-1187?

CVE-2015-1187 is a critical command injection vulnerability in n/a, published on 21 Sep 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The ping tool in multiple D-Link and TRENDnet devices allow remote attackers to execute arbitrary code via the ping_addr parameter to ping.ccp.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2015-1187?

It affects 15 products.


Products: Dlink Dir-626l Firmware, Dlink Dir-636l Firmware, Dlink Dir-651 Firmware, Dlink Dir-808l Firmware, Dlink Dir-810l Firmware, Dlink Dir-820l Firmware, Dlink Dir-826l Firmware, Dlink Dir-830l Firmware, Dlink Dir-836l Firmware, Trendnet Tew-651br Firmware, Trendnet Tew-652br Firmware, Trendnet Tew-711br Firmware, Trendnet Tew-731br Firmware, Trendnet Tew-810dr Firmware, Trendnet Tew-813dru Firmware.

## How do I fix CVE-2015-1187?

No fix has been published for CVE-2015-1187 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 15 Apr 2022.

## Is CVE-2015-1187 being exploited?

Yes. Attackers have exploited CVE-2015-1187 in the wild since at least 25 Mar 2022.

Public exploit code:

- D-Link/TRENDnet - NCC Service Command Injection (Metasploit) (exploitdb)
- D-Link/TRENDnet NCC Service Command Injection (metasploit)
- Independent reverse engineering and reproduction of CVE-2015-1187, an unauthenticated command injection in the D-Link DIR-820L (Rev A, v1.05B03). MIPS firmware extraction with binwalk, static analysis in Ghidra, and tracing the `ping_addr` parameter to its command-execution sink. (github_poc): https://github.com/christopher-leese/cve-2015-1187-dir820l-firmware-reverse-engineering

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-1187 and fix it if it is affected.

What it is: CVE-2015-1187 is a critical command injection vulnerability in n/a, published on 21 Sep 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2015-1187 in the wild since at least 25 Mar 2022.

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

## Sources

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

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