Dsp W215 FirmwareOperating system · Dlink

CVE-2021-29295

HIGH · 7.5 CVSS v3.1 Published 2021-08-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
Null Pointer Dereference vulnerability exists in D-Link DSP-W215 1.10, which could let a remote malicious user cause a denial of servie via usr/bin/lighttpd. It could be triggered by sending an HTTP request without URL in the start line directly to the device. NOTE: The DSP-W215 and all hardware revisions is considered End of Life and as such this issue will not be patched

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 null pointer dereference vulnerability exists in the lighttpd web server (usr/bin/lighttpd) on D-Link DSP-W215 devices version 1.10. The vulnerability can be triggered by sending a specially crafted HTTP request that lacks a URL in the request line, causing the web server to crash and result in a denial of service.

MitigationSince this device is End of Life and will not receive a firmware patch, implement network-level controls (firewall/IPS rules) to block malformed HTTP requests, or replace the affected device with a supported model.

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.10

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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. Confirm device model
    Check the physical device label or login to the device admin interface to verify the model number is D-Link DSP-W215
    Affected if Device model is not D-Link DSP-W215 - not affected
  2. Check firmware version
    Access the device admin web interface, typically at 192.168.0.1, and navigate to the firmware or status page to determine the installed firmware version
    Affected if Firmware version is not 1.10 - not affected
  3. Identify web server binary
    Use SSH or telnet to access the device shell and run 'ps' or check /proc to identify if lighttpd (usr/bin/lighttpd) is running as the web server process
    Affected if lighttpd is not running as the web server - not affected
  4. Verify web service accessibility
    Attempt to access the device web interface over HTTP on the standard port (80) to confirm the lighttpd service is actively listening
    Affected if Web service is not accessible or not running - not affected

The environment is affected only if the device is a D-Link DSP-W215 running firmware version 1.10 with the lighttpd web server actively running and accessible.

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

Since this device is End of Life and will not receive a firmware patch, implement network-level controls (firewall/IPS rules) to block malformed HTTP requests, or replace the affected device with a supported model.

Recommended fix High confidence
  1. This vulnerability will not be patched as the D-Link DSP-W215 is End of Life (EOL).
  2. Replace the EOL DSP-W215 device with a currently supported model from D-Link or another vendor.
  3. If immediate replacement is not possible, place the device behind a firewall and restrict network access to trusted users only to minimize exposure to remote attacks.
  4. Monitor vendor announcements for any future security updates (though none are currently planned for this EOL product).
Caveat The DSP-W215 is End of Life and has no firmware updates available; device replacement is required

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-2021-29295 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-2021-29295 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