CVE-2008-1522
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 and P-661 models with firmware 3.40(AGD.2) through 3.40(AHQ.3), have (1) "user" as their default password for the "user" account and (2) "1234" as their default password for the "admin" account, which makes it easier for remote attackers to obtain access.
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 P-660 and P-661 routers with firmware versions 3.40(AGD.2) through 3.40(AHQ.3) ship with hardcoded default credentials. The 'user' account uses password 'user' and the 'admin' account uses password '1234'. These credentials are exploitable remotely by attackers to gain unauthorized administrative access to the router.
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
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/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 router modelAccess the router web interface (typically 192.168.1.1) or log in via Telnet/SSH and check the device model name in the status or system info pageAffected if Router model is Prestige 660 or Prestige 661 (or related Zynos devices)
-
Check firmware versionIn the router web interface, navigate to Status or System Summary page to view the firmware version. Alternatively, use telnet to access the device and run the 'sys info' or 'show version' commandAffected if Firmware version is 3.40(AGD.2), 3.40(AGD.3), 3.40(AHQ.1), 3.40(AHQ.2), 3.40(AHQ.3) or falls within the 3.40 family that includes these variants
-
Test default user credentialsAttempt to log into the router web interface or via telnet using username 'user' with password 'user'Affected if Login succeeds with the default user/user credentials (indicating credentials have not been changed)
-
Test default admin credentialsAttempt to log into the router web interface or via telnet using username 'admin' with password '1234'Affected if Login succeeds with the default admin/1234 credentials (indicating credentials have not been changed)
Router is affected if it is a ZyXEL Prestige 660/661 or Zynos device running firmware version 3.40(AGD.2) through 3.40(AHQ.3) AND either the user or admin account still has the factory default password set.
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 dataImmediately change the default credentials for both user and admin accounts on affected routers. Disable remote administration interfaces if not required, and update to patched firmware if 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-2008-1522 — 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-1522 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