CVE-2005-3725
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 Version 1 VOIP WIFI Phone Wj.00.10 uses hardcoded IP addresses for its DNS servers, which could allow remote attackers to cause a denial of service or hijack Zyxel phones by attacking or spoofing the hardcoded DNS servers. NOTE: it could be argued that this issue reflects an inherent limitation of DNS itself, so perhaps it should not be included in CVE.
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 · moderate confidenceThe Zyxel P2000W Version 1 VOIP WIFI Phone firmware contains hardcoded DNS server IP addresses. An attacker who can compromise or spoof these hardcoded DNS servers could perform DNS hijacking attacks to redirect VOIP traffic or cause denial of service by making the DNS servers unavailable.
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= wj.00.10CVSS 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
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/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 the device modelLocate the physical device or check network inventory for Zyxel P2000W or Zyxel Prestige 2000w VoIP WiFi phone. Confirm the model number printed on the device or visible in management interfaces.Affected if The device is a Zyxel P2000W or Prestige 2000w variant.
-
Check the firmware versionAccess the device admin interface or console and retrieve the firmware version. Compare it to the affected version wj.00.10.Affected if The firmware version is exactly wj.00.10.
-
Verify if DNS servers are configurableNavigate to the device network or VoIP settings in the web admin interface or CLI. Look for DNS server configuration options. Attempt to change the DNS servers and save the settings.Affected if DNS server fields are not present or grayed out, or changes cannot be saved, indicating hardcoded DNS.
-
Inspect current DNS configurationCheck the device status page or run network diagnostics to see which DNS servers the device is using. Capture network traffic to observe DNS queries sent by the device.Affected if The device uses DNS server IPs that cannot be changed and appear to be hardcoded in the firmware.
-
Review firmware configuration filesIf firmware extraction is possible, examine configuration files or strings within the firmware image for hardcoded IP addresses used as DNS servers.Affected if Firmware contains static DNS IP addresses with no provision for user configuration.
If the device is a Zyxel P2000W/Prestige 2000w running firmware wj.00.10 and the DNS servers cannot be configured (they are hardcoded), the environment is affected by this CVE.
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 dataIf available, update to a patched firmware version from Zyxel that allows configurable DNS servers. If no update exists, consider network-level compensating controls such as deploying secure DNS (DoT/DoH) or network segmentation, or replace the device with a supported model.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.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 $2,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-3725 — 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-2005-3725 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