CVE-2004-2377
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 · uneditedAlcatel OmniSwitch 7000 and 7800 allows remote attackers to cause a denial of service (reboot) via certain network scans, as demonstrated using a Nessus port scan of ports 1 through 1024 with safe-checks disabled.
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 confidenceThe Alcatel OmniSwitch 7000 and 7800 network switches contain a vulnerability where certain network port scans (specifically Nessus scans of ports 1-1024 with safe-checks disabled) cause the devices to reboot, resulting in denial of service. This appears to be a flaw in how the switch handles certain network probe traffic.
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= 7000all versionsCVSS 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 device modelCheck the device identification using SNMP (snmpwalk on sysDescr.0 or sysObjectID.0), console login, or network discovery. Look for 'Alcatel OmniSwitch 7000' or 'Alcatel OmniSwitch 7800' in the output.Affected if The device is an Alcatel OmniSwitch 7000 or OmniSwitch 7800 series switch.
-
Check the firmware versionLog into the device CLI and run 'show software' or 'show version' to retrieve the installed firmware version. Alternatively, query via SNMP using snmpget on enterprises.6486.1.1.1.1.2.0 for version information.Affected if The device is running firmware that has not been patched by Alcatel for this vulnerability.
-
Verify network exposure to untrusted networksReview network topology and access control lists (ACLs) to determine if the switch management interfaces or network ports are reachable from untrusted networks. Check firewall rules and border router ACLs that permit inbound traffic to the switch from external or untrusted segments.Affected if The switch is directly accessible from networks where untrusted or unauthorized port scanning could occur (such as the internet or untrusted DMZ segments).
A defender is affected if they have an Alcatel OmniSwitch 7000 or 7800 switch that is reachable from untrusted networks and is running an unpatched firmware version vulnerable to DoS from port scan probes.
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 the appropriate Alcatel firmware patch for this vulnerability. If no patch is available, consider network segmentation or firewall rules to limit exposure to untrusted network scans, and contact Alcatel support for vendor-specific guidance.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2004-2377 — 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-2377 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