iOSOperating system · Cisco
CVE-2008-3807
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 · uneditedCisco IOS 12.2 and 12.3 on Cisco uBR10012 series devices, when linecard redundancy is configured, enables a read/write SNMP service with "private" as the community, which allows remote attackers to obtain administrative access by guessing this community and sending SNMP requests.
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 confidenceWhen linecard redundancy is configured on Cisco uBR10012 series CMTS devices running IOS 12.2 or 12.3, the system exposes a read/write SNMP service using the default 'private' community string. This default credential allows remote attackers who guess or know this community string to obtain full administrative access to the device via SNMP write operations.
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
iOSOperating system
= 12.2bc= 12.2cx= 12.2cy= 12.2xf= 12.3bcCVSS 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
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/Au:N/C:C/I:C/A:C
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 modelUse 'show version' or 'show hardware' command to confirm the device is a Cisco uBR10012 series CMTSAffected if Device is NOT a Cisco uBR10012 series CMTS - not affected
-
Check the IOS versionUse 'show version' to display the running IOS version and compare it to the affected versions: 12.2bc, 12.2cx, 12.2cy, 12.2xf, or 12.3bcAffected if IOS version does NOT match any of the affected versions - not affected
-
Verify linecard redundancy is configuredUse 'show redundancy' or check the running configuration for linecard redundancy settingsAffected if Linecard redundancy is NOT configured - not affected (vulnerability requires this feature to be enabled)
-
Check SNMP configuration for community stringsUse 'show snmp community' or 'show running-config | include snmp' to list configured SNMP community stringsAffected if The 'private' community string is present and configured for write access - POTENTIALLY AFFECTED
-
Confirm SNMP write access is enabledReview the SNMP community string configuration to determine if write access (rw) is granted to the 'private' community stringAffected if 'private' community string has read-write (rw) permissions - AFFECTED
User is affected if the device is a Cisco uBR10012 running IOS 12.2bc, 12.2cx, 12.2cy, 12.2xf, or 12.3bc, has linecard redundancy configured, and has the default 'private' community string configured with read-write SNMP access.
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 'private' to strong, unique values, disable SNMP if not required, or migrate to SNMPv3 with authentication and encryption. Additionally, restrict SNMP access via ACLs to trusted management hosts.
Fix this in iOS
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2008-3807 — 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-3807 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