# CVE-2021-29295: Null dereference in n/a

> Remote attackers can cause denial of service on D-Link DSP-W215 smart plugs by sending malformed HTTP requests, with no patch available due to end-of-life status.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 10 Aug 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-qrj4-928f-f3h2

## What is CVE-2021-29295?

CVE-2021-29295 is a high-severity vulnerability in n/a, published on 10 Aug 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2021-29295?

It affects 1 product.


Products: Dlink Dsp-W215 Firmware.

## How do I fix CVE-2021-29295?

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

## Is CVE-2021-29295 being exploited?

There is no known exploitation of CVE-2021-29295 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2014-125117](https://insights.sbomify.com/CVE-2014-125117/): D-Link info.cgi POST Request Stack-Based Buffer Overflow RCE (critical 9.3)
- [CVE-2020-13136](https://insights.sbomify.com/CVE-2020-13136/): Information disclosure in n/a (high 7.5)
- [CVE-2020-13135](https://insights.sbomify.com/CVE-2020-13135/): Information disclosure in n/a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-29295 and fix it if it is affected.

What it is: CVE-2021-29295 is a high-severity vulnerability in n/a, published on 10 Aug 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-29295 in the wild and no public exploit code.

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

## Sources

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

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