Optical Networking Systems SoftwareApplication · Cisco
CVE-2004-1432
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 · uneditedMultiple versions of Cisco ONS 15327, ONS 15454, and ONS 15454 SDH, including 4.6(0) and 4.6(1), 4.5(x), 4.1(0) to 4.1(3), 4.0(0) to 4.0(2), and earlier versions, allows remote attackers to cause a denial of service (control card reset) via malformed (1) IP or (2) ICMP packets.
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 confidenceMultiple Cisco ONS (Optical Network System) platforms (15327, 15454, 15454 SDH) are vulnerable to denial of service via malformed IP or ICMP packets that trigger a control card reset.
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
Optical Networking Systems SoftwareApplication
= 1.0= 1.1= 1.1\(0\)= 1.1\(1\)= 1.3\(0\)= 2.3\(5\)= 3.0= 3.1.0= 3.2= 3.2.0= 3.3.0= 3.4.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Cisco ONS hardware platformUse 'show version' or check physical labeling to confirm the device model is Cisco ONS 15327, 15454, or 15454 SDHAffected if Device is any of these three platforms
-
Retrieve Cisco ONS software versionConnect to the ONS controller via console or network management interface and execute 'show version' or use TL1 command 'RTRV-VERSION' to obtain the installed software versionAffected if Software version cannot be retrieved or shows an ONS platform
-
Compare installed version to affected listMatch the retrieved version against these affected versions: 1.0, 1.1, 1.1(0), 1.1(1), 1.3(0), 2.3(5), 3.0, 3.1.0, 3.2, 3.2.0, 3.3.0, 3.4.0Affected if Installed version matches any of these specific versions exactly
-
Verify exposure to network trafficConfirm the ONS device has IP or ICMP network interfaces enabled and is exposed to external network trafficAffected if Device processes IP or ICMP packets from untrusted networks
User is affected if the device is a Cisco ONS 15327, 15454, or 15454 SDH running any of the listed versions and has active network interfaces processing IP/ICMP traffic.
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 dataApply appropriate Cisco patches or upgrade to a patched version; consider network filtering to block malformed packets at network perimeter.
Fix this in Optical Networking Systems Software
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2004-1432 — 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-2004-1432 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