CVE-2008-1524
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 · uneditedThe SNMP service on ZyXEL Prestige routers, including P-660 and P-661 models with firmware 3.40(AGD.2) through 3.40(AHQ.3), has "public" as its default community for both (1) read and (2) write operations, which allows remote attackers to perform administrative actions via SNMP, as demonstrated by reading the Dynamic DNS service password or inserting an XSS sequence into the system.sysName.0 variable, which is displayed on the System Status page.
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 SNMP service on ZyXEL Prestige routers (P-660, P-661 models) with firmware 3.40(AGD.2) through 3.40(AHQ.3) uses 'public' as the default community string for both read AND write operations, allowing remote attackers to perform administrative actions such as reading sensitive data like Dynamic DNS passwords or injecting XSS payloads into the system.sysName.0 OID.
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 the device modelAccess the router web interface or use SNMP to query the sysDescr.0 OID (1.3.6.1.2.1.1.1.0) - look for 'Prestige 660', 'Prestige 661', or 'Zynos' in the responseAffected if The device is a ZyXEL Prestige 660, Prestige 661, or Zynos router
-
Check the firmware versionVia web interface under 'Firmware' or 'Status' page, or query the sysUptime.0 OID and compare to the firmware release notes. The affected range is 3.40(AGD.2) through 3.40(AHQ.3)Affected if The firmware version falls within 3.40(AGD.2) to 3.40(AHQ.3) inclusive
-
Verify SNMP is enabledCheck the router web interface under 'SNMP' or 'Management' settings, or attempt to query the SNMP service on the router's IP address on port 161/udpAffected if SNMP service is enabled and responding to queries
-
Inspect SNMP community string configurationIn the SNMP settings page of the router web interface, examine the configured community strings for read and write operations. Compare against the default value 'public'Affected if The community string is set to the default value 'public' for read-write access
The environment is affected if it is a ZyXEL Prestige 660/661 or Zynos router running firmware between 3.40(AGD.2) and 3.40(AHQ.3) with SNMP enabled and the default community string 'public' still configured.
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 dataChange the default SNMP community strings from 'public' to strong, unique values and disable SNMP write access if not required; consider disabling SNMP entirely if unused.
- Consultation2.0 h
- Implementation1.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,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2008-1524 — 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-1524 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