dbcve.org
iOSOperating system · Cisco

CVE-2006-4950

HIGH · 10.0 CVSS v2.0 Published 2006-09-23
Fix available
A fix is available. Upgrade to after 12.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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 · unedited
Cisco IOS 12.2 through 12.4 before 20060920, as used by Cisco IAD2430, IAD2431, and IAD2432 Integrated Access Devices, the VG224 Analog Phone Gateway, and the MWR 1900 and 1941 Mobile Wireless Edge Routers, is incorrectly identified as supporting DOCSIS, which allows remote attackers to gain read-write access via a hard-coded cable-docsis community string and read or modify arbitrary SNMP variables.

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

A detailed technical summary for this CVE is being prepared.

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
Affected:<= 12.3= 12.3\(1a\)= 12.3\(2\)ja= 12.3\(2\)ja5= 12.3\(2\)jk= 12.3\(2\)jk1= 12.3\(2\)t3= 12.3\(2\)t8= 12.3\(2\)xa4= 12.3\(2\)xa5= 12.3\(2\)xc1= 12.3\(2\)xc2

CVSS 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
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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.

dbcve · scoped
Upgrade available Upgrade to a release after 12.3
Vendor patch secunia.com →
Recommended fix High confidence

Cisco IOS 12.4 or later (post-September 2006) - specific version depends on device model; consult Cisco IOS upgrade path tool for exact recommended release

  1. 1. Identify the exact Cisco device model (IAD2430, IAD2431, IAD2432, VG224, MWR1900, or MWR1941) in your environment
  2. 2. Access the Cisco IOS upgrade path tool or Cisco Software Checker to find the recommended fixed release for your specific device
  3. 3. Download the appropriate Cisco IOS version 12.4 or later (post-September 2006) from Cisco's official software download center
  4. 4. Back up the current device configuration
  5. 5. Upload the new IOS image to the device following standard Cisco upgrade procedures
  6. 6. Reload the device to apply the new image
  7. 7. Verify the device is functioning properly post-upgrade
  8. 8. Change any SNMP community strings from the default 'cable-docsis' to a unique, strong community string
Caveat Review Cisco release notes for your device to check for any configuration incompatibilities or feature changes between your current version and the target 12.4 release

Generated from the published advisory — verify against the referenced sources before acting.

We can identify the exact fixed release, upgrade, and verify it in staging — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2006-4950 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2006-4950 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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