# CVE-2006-3687: Memory corruption in n/a

> Remote attackers can execute arbitrary code on D-Link routers via a stack-based buffer overflow in the UPnP service.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Jul 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-w54f-j9wc-72mq

## What is CVE-2006-3687?

CVE-2006-3687 is a high-severity memory corruption vulnerability in n/a, published on 18 Jul 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Stack-based buffer overflow in the Universal Plug and Play (UPnP) service in D-Link DI-524, DI-604 Broadband Router, DI-624, D-Link DI-784, WBR-1310 Wireless G Router, WBR-2310 RangeBooster G Router, and EBR-2310 Ethernet Broadband Router allows remote attackers to execute arbitrary code via a long M-SEARCH request to UDP port 1900.

## Which versions are affected by CVE-2006-3687?

It affects 7 products.


Products: D-Link Di-604 Broadband Router, D-Link Di-784, D-Link Ebr-2310 Ethernet Broadband Router, D-Link Wbr-1310 Wireless G Router, D-Link Wbr-2310 Rangebooster G Router, Dlink Di-524, Dlink Di-624.

## How do I fix CVE-2006-3687?

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

## Is CVE-2006-3687 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-3687 exists.

Public exploit code:

- D-Link Routers - UPNP Buffer Overflow (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-3687 and fix it if it is affected.

What it is: CVE-2006-3687 is a high-severity memory corruption vulnerability in n/a, published on 18 Jul 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-3687 exists.

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

## Sources

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

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