CVE-2008-1525
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 default SNMP configuration on ZyXEL Prestige routers, including P-660 and P-661 models with firmware 3.40(AGD.2) through 3.40(AHQ.3), has a Trusted Host value of 0.0.0.0, which allows remote attackers to send SNMP requests from any source IP address.
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 default SNMP configuration on ZyXEL Prestige routers (P-660, P-661 models) with firmware versions 3.40(AGD.2) through 3.40(AHQ.3) sets the Trusted Host value to 0.0.0.0, effectively disabling IP-based access control for SNMP. This allows any remote attacker to send SNMP requests to the device, potentially exposing sensitive network configuration and system information.
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
- None
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:N/I:P/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 router modelAccess the router's web interface or check the device label to confirm it is a ZyXEL Prestige 660 or 661 modelAffected if Device is not a ZyXEL Prestige 660 or 661 model - this vulnerability only applies to those specific models
-
Check the firmware versionLog into the router's web interface and navigate to the firmware or status page to determine the installed firmware versionAffected if Firmware version is NOT within the 3.40 branch (for example, 3.40(AGD.2) through 3.40(AHQ.3)) - versions outside this range are not affected
-
Confirm SNMP is enabledAccess the router's SNMP configuration page (typically under Management or Advanced Settings) and verify that the SNMP service is turned onAffected if SNMP is disabled on the router - the vulnerability requires SNMP to be enabled to be exploitable
-
Inspect the SNMP Trusted Host settingIn the SNMP configuration page, locate the Trusted Host or Access Control setting and verify whether it is set to 0.0.0.0 (any IP address)Affected if Trusted Host is set to 0.0.0.0 - this configuration disables IP-based access control and allows any remote attacker to send SNMP requests to the device
A user is affected if they have a ZyXEL Prestige 660/661 router running firmware version 3.40 with SNMP enabled and the Trusted Host setting configured as 0.0.0.0
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 SNMP Trusted Host setting from 0.0.0.0 to specific authorized IP addresses (or IP ranges) in the router's SNMP configuration, or disable SNMP entirely if not required.
- Consultation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2008-1525 — 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-1525 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