CVE-2004-1433
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, and ONS 15600 1.x(x), allows remote attackers to cause a denial of service (control card reset) via malformed (1) TCP and (2) UDP 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 confidenceThis is a denial of service vulnerability in Cisco Optical Networking System (ONS) devices. Remote attackers can send malformed TCP or UDP packets to affected ONS 15327, ONS 15454, ONS 15454 SDH, and ONS 15600 devices, causing the control card to reset and service disruption.
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= 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 the ONS device modelLog into the device or check inventory records to determine if the device is one of: ONS 15327, ONS 15454, ONS 15454 SDH, or ONS 15600Affected if The device is any of these four models and is directly accessible on the network
-
Check the software versionUse the device console or CLI command 'show version' or 'show software' to retrieve the installed Optical Networking Systems Software versionAffected if The installed version matches any of: 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, or 3.4.0
-
Verify network accessibility of management interfacesCheck firewall rules, ACLs, or network segmentation to determine if the ONS device management ports (typically TCP/UDP ports used for ONS protocols) are exposed to untrusted networks or the internetAffected if The device management interfaces accept TCP or UDP packets from untrusted or external network sources
-
Check for recent control card resetsReview system logs, using commands such as 'show logging' or 'show alarm history', for unexpected control card resets or reload eventsAffected if Recent control card resets or service disruptions have occurred without an administrator-initiated reload
You are affected if you run any of the listed software versions on an ONS 15327, 15454, 15454 SDH, or 15600 device that has its management interfaces accessible over TCP or UDP from untrusted networks.
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 Cisco-provided firmware patches for affected versions. If patches are unavailable, consider network segmentation and firewall rules to restrict untrusted traffic to ONS management interfaces.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2004-1433 — 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-1433 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