CVE-2006-0302
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 · uneditedZyXel P2000W VoIP 802.11b Wireless Phone running firmware WV.00.02 allows remote attackers to obtain sensitive information, such as MAC address and software version, by directly accessing UDP port 9090.
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 ZyXel P2000W VoIP wireless phone firmware WV.00.02 exposes sensitive device information including MAC address and software version through UDP port 9090 without requiring authentication. An attacker with network access to the device can directly query this port to enumerate device details.
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= wv.00.02CVSS 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
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
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 modelPhysically inspect the device or query the device's web interface or network services to confirm it is a Zyxel P2000W Version 2 VoIP WiFi phoneAffected if The device is a Zyxel P2000W Version 2 phone
-
Verify the firmware versionAccess the device's web interface, check the device label, or query the device using manufacturer-provided tools to determine the installed firmware versionAffected if The firmware version is WV.00.02
-
Check if UDP port 9090 is accessibleUse a network scanning tool such as nmap or netcat to test connectivity to UDP port 9090 on the device (for example: nmap -sU -p 9090 <device_ip>)Affected if UDP port 9090 is open and accepting connections
-
Query UDP port 9090 for sensitive informationSend a UDP packet to port 9090 on the device and observe the response - look for MAC address or software version information returned without authenticationAffected if The device responds with MAC address or software version information without requiring any authentication
The environment is affected if the device is a Zyxel P2000W Version 2 phone running firmware WV.00.02 and UDP port 9090 is accessible on the network, as the device will reveal sensitive information to any unauthenticated query.
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 dataRestrict or block external access to UDP port 9090 via firewall rules or network ACLs. If the device is still in use, consider network segmentation to limit exposure and verify if vendor firmware updates are available.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-0302 — 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-0302 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