dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 15 Apr 2022.
Dir 626l FirmwareOperating system · Dlink

CVE-2015-1187

CRITICAL · 9.8 CVSS v3.1 Published 2017-09-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Command injection vulnerability in the ping functionality of D-Link and TRENDnet embedded devices. The ping_addr parameter in ping.ccp is not properly sanitized, allowing attackers to inject arbitrary OS commands that are executed with root privileges on the device.

MitigationApply vendor-provided firmware updates from D-Link and TRENDnet. If patches are unavailable, disable remote management interfaces or place affected devices behind a firewall to reduce exposure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Dir 626l FirmwareOperating system
Affected:= 1.04
Dir 636l FirmwareOperating system
Affected:= 1.04
Dir 808l FirmwareOperating system
Affected:= 1.03
Dir 810l FirmwareOperating system
Affected:= 1.01= 2.02
Dir 820l FirmwareOperating system
Affected:= 1.02= 1.05= 2.01
Dir 826l FirmwareOperating system
Affected:= 1.00
Dir 830l FirmwareOperating system
Affected:= 1.00
Dir 836l FirmwareOperating system
Affected:= 1.01

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Determine if the device is a D-Link DIR series router (models 626l, 636l, 808l, 810l, 820l, 826l, 830l, or 836l) by checking the device label, web interface, or administrative console.
    Affected if The device is one of the listed D-Link models.
  2. Check the installed firmware version
    Access the router web interface (typically at 192.168.0.1) and navigate to the Status or Administration section to view the firmware version. Alternatively, check the device documentation or firmware file name.
    Affected if The firmware version matches exactly one of the following: 1.04 (Dir 626l/636l), 1.03 (Dir 808l), 1.01 or 2.02 (Dir 810l), 1.02, 1.05, or 2.01 (Dir 820l), 1.00 (Dir 826l/830l), or 1.01 (Dir 836l).
  3. Verify ping tool accessibility
    Attempt to access the ping functionality on the device. This is typically found in the web interface under Tools, Network Tools, or Diagnostic settings, often via a ping.ccp or similar endpoint.
    Affected if The ping tool is exposed and accessible on the network (either from LAN or WAN interface).
  4. Confirm ping.ccp endpoint exists
    Check if the device responds to requests targeting the ping.ccp endpoint (e.g., by observing the router's web interface or checking for CGI binaries).
    Affected if The ping.ccp endpoint is present and reachable on the device.

A user is affected if they are using one of the specified D-Link DIR device models with a firmware version matching the listed affected versions and the ping tool (ping.ccp) is accessible on their network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-provided firmware updates from D-Link and TRENDnet. If patches are unavailable, disable remote management interfaces or place affected devices behind a firewall to reduce exposure.

Recommended fix Low confidence

Check D-Link support for latest available firmware for your specific model (these older DIR series devices from ~2014-2015 may be end-of-life and no longer receiving updates)

  1. 1. Identify the exact model number (DIR 626l, 636l, 808l, 810l, 820l, 826l, 830l, or 836l) of the affected D-Link device
  2. 2. Check D-Link's official support page (support.dlink.com) for the specific model to see if newer firmware is available
  3. 3. If a newer firmware version is available, download it from the official D-Link support site only
  4. 4. Access the router's web interface using a wired connection
  5. 5. Navigate to the firmware upgrade section (typically under Administration or Maintenance)
  6. 6. Upload and apply the new firmware version
  7. 7. After upgrade, verify the ping.ccp vulnerability is no longer exploitable
  8. 8. If no firmware update is available from D-Link, consider replacing the device with a currently supported model
Caveat Old firmware may not be recoverable if upgrade fails; ensure stable power during firmware flash; some older devices may not have any firmware updates available

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Dir 626l Firmware Exploited in the wild — priority engagement
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,320.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-1187 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-1187 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data