dbcve.org
Transport ControllerApplication · Cisco

CVE-2006-1671

MEDIUM · 5.0 CVSS v2.0 Published 2006-04-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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
Control cards for Cisco Optical Networking System (ONS) 15000 series nodes before 20060405 allow remote attackers to cause a denial of service (card reset) via (1) a "crafted" IP packet to a device with secure mode EMS-to-network-element access, aka bug ID CSCsc51390; (2) a "crafted" IP packet to a device with IP on the LAN interface, aka bug ID CSCsd04168; and (3) a "malformed" OSPF packet, aka bug ID CSCsc54558.

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 confidence

Denial of service vulnerability in Cisco ONS 15000 series optical networking nodes allows remote attackers to cause card resets via three vectors: crafted IP packets targeting devices with secure mode EMS-to-network-element access, crafted IP packets to devices with IP on the LAN interface, and malformed OSPF packets. The vulnerability affects versions prior to the 20060405 patch release.

MitigationUpgrade Cisco ONS 15000 series nodes to firmware versions released on or after April 5, 2006. Additionally, filter or disable OSPF on the affected interfaces if not required, and implement network segmentation to limit exposure of the optical networking elements to untrusted networks.

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
Transport ControllerApplication
Affected:= 4.0.x
Optical Networking Systems SoftwareApplication
Affected:= 1.0= 1.1= 1.1\(0\)= 1.1\(1\)= 1.3\(0\)= 3.0= 3.1.0= 3.2= 3.3.0= 3.4.0= 4.0\(1\)= 4.0\(2\)
Ons 15310 Cl SeriesHardware / appliance
Affected:= 0
Ons 15600Hardware / appliance
Affected:= 0
Ons 15454 MsppOperating system
Affected:all versions

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
None
Integrity
None
Availability
Partial

AV:N/AC:L/Au:N/C:N/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Cisco ONS device model
    Query the device hardware inventory or use 'show version' command to confirm the device is an ONS 15000 series node (ONS 15310, ONS 15600, or ONS 15454)
    Affected if Device is not an ONS 15000 series platform - not affected
  2. Check installed software version
    Use 'show version' or access Cisco Transport Controller to determine the exact software/firmware version. Compare against the affected versions: Cisco Transport Controller 4.0.x, Cisco Optical Networking Systems Software versions 1.0 through 4.0(2), and any version of ONS 15454 MSPP
    Affected if Running any version prior to the 20060405 patch release or version not listed as fixed
  3. Verify IP configuration on LAN interface
    Check device network configuration for any IP address assigned to the LAN interface using 'show ip interface' or through CTC network settings
    Affected if IP address is configured on the LAN interface - vulnerable to crafted IP packet attack vector
  4. Check if secure mode EMS access is enabled
    Review EMS-to-network-element access configuration in Cisco Transport Controller or via CLI to determine if secure mode access is configured
    Affected if Secure mode EMS-to-network-element access is enabled - vulnerable to crafted IP packet attack vector
  5. Verify OSPF protocol configuration
    Check running configuration or use 'show ip ospf' to determine if OSPF is enabled on any interface
    Affected if OSPF is enabled and running - vulnerable to malformed OSPF packet attack vector

Device is affected if it is a Cisco ONS 15000 series node running software versions prior to the April 5, 2006 patch release AND has at least one of these enabled: IP on LAN interface, secure mode EMS access, or OSPF protocol.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Cisco ONS 15000 series nodes to firmware versions released on or after April 5, 2006. Additionally, filter or disable OSPF on the affected interfaces if not required, and implement network segmentation to limit exposure of the optical networking elements to untrusted networks.

Fix this in Transport Controller Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2006-1671 — 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-1671 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