CVE-2006-6411
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 · uneditedPhoneCtrl.exe in Linksys WIP 330 Wireless-G IP Phone 1.00.06A allows remote attackers to cause a denial of service (crash) via a TCP SYN scan, as demonstrated using TCP ports 1-65535 with nmap.
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 PhoneCtrl.exe service in the Linksys WIP 330 Wireless-G IP Phone firmware 1.00.06A crashes when receiving a TCP SYN scan across ports 1-65535. The service fails to properly handle the high volume of SYN packets during a port scan, causing a denial of service condition.
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= 1.0.6_aCVSS 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
- Complete
AV:N/AC:L/Au:N/C:N/I:N/A:C
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 device modelDetermine if the target device is a Linksys WIP 330 Wireless-G IP Phone. This can be done by checking device labels, network inventory, or accessing the device web interface/admin panel.Affected if The device is a Linksys WIP 330 Wireless-G IP Phone
-
Check the firmware versionAccess the device admin interface or check via SNMP/network management tools to retrieve the installed firmware version.Affected if The firmware version is 1.00.06A (also shown as 1.0.6_a)
-
Verify the PhoneCtrl.exe service is runningAccess the device via telnet, SSH, or remote management interface and check if the PhoneCtrl.exe process/service is active.Affected if The PhoneCtrl.exe service is running and accessible
-
Assess network exposure to TCP scanningDetermine if the device is directly accessible from untrusted networks. Check firewall rules, ACLs, or network segmentation that may permit or block inbound TCP connections to the device.Affected if The device is network-accessible and accepts inbound TCP connections from untrusted segments, allowing a port scan to reach it
You are affected if you have a Linksys WIP 330 Wireless-G IP Phone running firmware version 1.00.06A with the PhoneCtrl.exe service running and the device is accessible from a network where an attacker could perform a TCP SYN port scan.
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 any available firmware update from Linksys for this device. If no update exists, restrict network access to the IP phone via firewall rules or network segmentation to prevent unauthorized TCP scanning.
- Consultation3.0 h
- Implementation3.0 h
- Testing2.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 $2,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-6411 — 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-6411 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