dbcve.org
Dsp W215 FirmwareOperating system · Dlink

CVE-2014-125117

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-25
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
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
A stack-based buffer overflow vulnerability in the my_cgi.cgi component of certain D-Link devices, including the DSP-W215 version 1.02, can be exploited via a specially crafted HTTP POST request to the /common/info.cgi endpoint. This flaw enables an unauthenticated attacker to achieve remote code execution with system-level privileges.

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

A stack-based buffer overflow in the my_cgi.cgi component of D-Link DSP-W215 (v1.02) allows unauthenticated remote code execution via a crafted HTTP POST to /common/info.cgi. The overflow occurs in the web server handling, enabling attackers to overwrite stack memory and execute arbitrary code with system privileges.

MitigationApply the vendor firmware patch when available; alternatively, restrict network access to the /common/info.cgi endpoint via firewall rules or disable the affected service if not required.

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
Dsp W215 FirmwareOperating system
Affected:= 1.02

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 D-Link device model
    Access the device web interface or check the device label to confirm the exact model number is DSP-W215
    Affected if The device is not a D-Link DSP-W215 model
  2. Check the installed firmware version
    Log into the D-Link DSP-W215 web interface and navigate to the Status or Management page to view the firmware version, or use the command 'grep version /etc/os-release' or check the web page source for version strings
    Affected if The firmware version is 1.02 exactly
  3. Verify the /common/info.cgi endpoint is present
    Attempt to access 'http://[device-ip]/common/info.cgi' via HTTP GET request using curl or a browser. If the page loads or responds, the endpoint exists
    Affected if The endpoint responds with any content (indicating it is enabled and accessible)
  4. Confirm network exposure to the vulnerable endpoint
    Check if the device management interface (port 80/443) is directly accessible from external networks or the internet by reviewing firewall rules, NAT configurations, or port forwarding settings
    Affected if The device or /common/info.cgi endpoint is reachable from untrusted networks (WAN/internet) without firewall protection

A defender is affected if they have a D-Link DSP-W215 device running firmware version 1.02 with the /common/info.cgi endpoint 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 the vendor firmware patch when available; alternatively, restrict network access to the /common/info.cgi endpoint via firewall rules or disable the affected service if not required.

Recommended fix Moderate confidence

Latest DSP-W215 firmware available from D-Link support site (check for versions beyond 1.02)

  1. 1. Identify the exact model number (DSP-W215) and current firmware version by logging into the router web interface or checking the device label.
  2. 2. Visit the official D-Link support page at support.dlink.com and search for DSP-W215 firmware downloads.
  3. 3. Download the latest available firmware version from D-Link's official website - do not use third-party sources.
  4. 4. Access the router's web administration interface and navigate to the Firmware Upgrade or System section.
  5. 5. Upload the downloaded firmware file and allow the upgrade process to complete (typically 2-5 minutes).
  6. 6. After reboot, verify the new firmware version is installed and test that basic router functions work correctly.
  7. 7. If no newer firmware is available from D-Link, consider replacing the device as it may be end-of-life and no longer receiving security updates.
Caveat Firmware upgrades on older D-Link devices may reset configuration to defaults; backup current settings before upgrading and reconfigure after upgrade.

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

Fix this in Dsp W215 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-125117 — 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-2014-125117 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