SilkwormHardware / appliance · Brocade

CVE-2004-1663

MEDIUM · 5.0 CVSS v2.0 Published 2004-09-04
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
Engenio/LSI Logic storage controllers, as used in products such as Storagetek D280, and IBM DS4100 (formerly FastT 100) and Brocade SilkWorm Switches, allow remote attackers to cause a denial of service (freeze and possible data corruption) via crafted TCP 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 · moderate confidence

This vulnerability exists in Engenio/LSI Logic storage controllers used in Storagetek D280, IBM DS4100 (FastT 100), and Brocade SilkWorm Switches. Remote attackers can send crafted TCP packets to cause device freeze (denial of service) with potential data corruption.

MitigationIsolate affected storage devices behind firewalls or network segmentation to limit external attack surface; contact LSI/Engenio, IBM, and Brocade for available firmware patches for this 2004 vulnerability.

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
SilkwormHardware / appliance
Affected:= 3200= 3250= 3800= 3850= 3900
Silkworm Fiber Channel SwitchHardware / appliance
Affected:= 2010= 2040= 2050
Storage ControllerHardware / appliance
Affected:= 2822= 2882= 4884= 5884
Ds4100Hardware / appliance
Affected:all versions
D280Hardware / appliance
Affected:all versions
Fabric Operating SystemOperating system
Affected:= 2.1.2= 2.2= 3.1

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 hardware model
    Locate the storage controller or switch physical label or log into the management interface to view the model number. Common models include Brocade SilkWorm 3200/3250/3800/3850/3900, 2010/2040/2050; Engenio 2822/2882/4884/5884; IBM DS4100; Storagetek D280.
    Affected if The model matches one of the listed affected models: Brocade SilkWorm 3200, 3250, 3800, 3850, 3900, 2010, 2040, 2050; Engenio 2822, 2882, 4884, 5884; IBM DS4100; Storagetek D280.
  2. Check firmware or Fabric OS version
    Access the device management interface (CLI, web GUI, or SNMP) and retrieve the firmware or Fabric Operating System version. For Brocade switches, use 'version' or 'firmwareShow' command. For Engenio/IBM controllers, check via RAID controller management software.
    Affected if The firmware version matches: Brocade Fabric OS 2.1.2, 2.2, or 3.1; or for Engenio/LSI Logic controllers, firmware version matches 2822, 2882, 4884, or 5884.
  3. Confirm device is network accessible
    Verify that the management interface or TCP ports on the device are reachable from network segments accessible to untrusted users. Use ping, port scans, or review firewall rules and network ACLs.
    Affected if The device management interface or TCP services are exposed to untrusted networks, allowing remote attackers to send crafted TCP packets to the device.
  4. Verify IBM DS4100 or Storagetek D280
    If the device is an IBM DS4100 (FastT 100) or Storagetek D280, note that these are affected in all versions regardless of firmware level.
    Affected if The device is an IBM DS4100 (any version) or Storagetek D280 (any version) and is network-accessible.

A user is affected if they have any of the listed hardware models with matching versions (or any version for IBM DS4100/Storagetek D280) and the device is reachable over the network from untrusted actors.

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

Isolate affected storage devices behind firewalls or network segmentation to limit external attack surface; contact LSI/Engenio, IBM, and Brocade for available firmware patches for this 2004 vulnerability.

Fix this in Silkworm Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2004-1663 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2004-1663 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