CVE-2006-1067
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 · uneditedLinksys WRT54G routers version 5 (running VXWorks) allow remote attackers to cause a denial of service by sending a malformed DCC SEND string to an IRC channel, which causes an IRC connection reset, possibly related to the masquerading code for NAT environments, and as demonstrated via (1) a DCC SEND with a single long argument, or (2) a DCC SEND with IP, port, and filesize arguments with a 0 value.
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 confidenceThe Linksys WRT54G v5 router running VXWorks contains a vulnerability in its IRC masquerading/NAT traversal code. When the router processes malformed DCC SEND commands (either a single long argument or IP/port/filesize with zero values), it causes the router to reset the IRC connection, resulting in denial of service.
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 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
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/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 the router modelPhysically inspect the router label or access the admin interface to confirm the model number is WRT54G v5Affected if The device is a Linksys WRT54G version 5
-
Check the firmware operating systemAccess the router admin interface (typically at 192.168.1.1) and check the firmware version or OS information; VXWorks is typically displayed in the system info or boot logAffected if The router runs VXWorks as its embedded operating system
-
Verify IRC masquerading is enabledAccess the router admin interface, navigate to the NAT, port forwarding, or advanced routing settings, and check if IRC-related masquerading or NAT traversal features are enabledAffected if IRC masquerading or NAT traversal for IRC traffic is enabled in the router configuration
-
Confirm IRC traffic handlingCheck the router's connection tracking or firewall logs for active IRC connections passing through the NAT; examine any DCC-related rules or settingsAffected if The router is actively handling IRC traffic through its NAT/masquerading functionality
A user is affected if they own a Linksys WRT54G v5 router running VXWorks with IRC masquerading or NAT traversal enabled and are passing IRC traffic through the device.
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 dataSince this is an embedded firmware vulnerability in a discontinued 2006 router model, official patches are unlikely. Users should replace the end-of-life WRT54G v5 with a supported router, or implement network segmentation to isolate IRC traffic if continued use is required.
- Consultation2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-1067 — 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-1067 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