CVE-2006-3687
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 · uneditedStack-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.
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 confidenceStack-based buffer overflow in D-Link routers' UPnP service allows remote attackers to send specially crafted long M-SEARCH requests to UDP port 1900, potentially executing arbitrary code. The vulnerability affects multiple D-Link router models including DI-524, DI-604, DI-624, DI-784, WBR-1310, WBR-2310, and EBR-2310.
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 dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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 checksWork through these to decide whether this CVE applies to you.
-
Identify router modelCheck the device label or web interface for the exact model number (e.g., DI-524, DI-604, DI-624, DI-784, WBR-1310, WBR-2310, EBR-2310)Affected if The model matches one of the affected models: DI-524, DI-604, DI-624, DI-784, WBR-1310, WBR-2310, or EBR-2310
-
Verify UPnP service statusLog into the router web interface (typically 192.168.0.1 or 192.168.1.1) and navigate to Advanced or Setup settings to check if UPnP is enabledAffected if UPnP is turned ON in the router configuration
-
Confirm UDP port 1900 exposureUse a network scanner or the command 'nc -uz <router_ip> 1900' or 'nmap -sU -p 1900 <router_ip>' to test if UDP port 1900 is open and respondingAffected if UDP port 1900 is open and accepts M-SEARCH requests
-
Test for vulnerability with crafted M-SEARCHSend a UDP packet with an oversized M-SEARCH string to port 1900: echo -ne 'M-SEARCH * HTTP/1.1 Host:239.255.255.250:1900 Man:"ssdp:discover" MX:3 ST:urn:schemas-upnp-org:device:InternetGatewayDevice:1 AAAAAAAAAAAAAAAAAAA...' | nc -u <router_ip> 1900Affected if The device does not respond with a proper SSDP response or exhibits unexpected behavior (crash, restart, or no response)
The device is affected if it is a D-Link model among DI-524, DI-604, DI-624, DI-784, WBR-1310, WBR-2310, or EBR-2310, has UPnP enabled, and has UDP port 1900 exposed on the network.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataApply vendor firmware updates if available; otherwise, disable the UPnP service on affected devices to eliminate the attack surface.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-3687 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2006-3687 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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