CVE-2008-1523
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 Prestige routers, including P-660, P-661, and P-662 models with firmware 3.40(AGD.2) through 3.40(AHQ.3), allow remote authenticated users to obtain ISP and Dynamic DNS credentials by sending a direct request for (1) WAN.html, (2) wzPPPOE.html, and (3) rpDyDNS.html, and then reading the HTML source.
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 confidenceZyXEL Prestige routers (P-660, P-661, P-662) with firmware versions 3.40(AGD.2) through 3.40(AHQ.3) expose sensitive ISP username/password and Dynamic DNS credentials in plain text within HTML source code when authenticated users request WAN.html, wzPPPOE.html, or rpDyDNS.html pages.
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= h-d1= h-d3= hw-d1= 3.40CVSS 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 router modelAccess the router's web management interface and check the device information page, or log into the router CLI and run 'sys info' or similar command to confirm the model is ZyXEL Prestige 660, 661, 662, or a device running Zynos firmware.Affected if Device is not a ZyXEL Prestige router or Zynos device
-
Check firmware versionIn the router web interface, navigate to the Status or System Info page to view the firmware version. Compare the version number to the affected range: 3.40(AGD.2) through 3.40(AHQ.3).Affected if Firmware version falls within 3.40(AGD.2) to 3.40(AHQ.3) inclusive
-
Verify web management interface accessibilityConfirm that the router's HTTP/HTTPS web management interface is accessible from your network. Try accessing the router's IP address in a web browser.Affected if Web management interface is exposed and accessible
-
Inspect HTML source for exposed credentialsUsing an authenticated browser session, access the following pages: WAN.html, wzPPPOE.html, and rpDyDNS.html. For each page, view the page source (right-click > View Page Source) and search for plain text strings containing ISP username, ISP password, or Dynamic DNS credentials.Affected if ISP credentials or Dynamic DNS passwords appear in plain text within the HTML source code of any of these pages
You are affected if you have a ZyXEL Prestige router or Zynos device running firmware between 3.40(AGD.2) and 3.40(AHQ.3), and credentials are visible in plain text in the HTML source of WAN.html, wzPPPOE.html, or rpDyDNS.html pages.
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 dataUpgrade router firmware to a patched version if available; otherwise, restrict administrative access to trusted IP addresses only, change all exposed credentials immediately, and consider disabling remote management if not required.
- 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-2008-1523 — 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-2008-1523 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