# CVE-2004-2377: Denial of service in n/a

> Remote attackers can cause a denial of service reboot on Alcatel OmniSwitch devices by performing specific network scans.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Aug 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-hr3h-86gx-c4cp

## What is CVE-2004-2377?

CVE-2004-2377 is a medium-severity denial of service vulnerability in n/a, published on 16 Aug 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Alcatel 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.

## Which versions are affected by CVE-2004-2377?

It affects 2 products.


Products: Alcatel Omniswitch, Alcatel Omniswitch 7800.

## How do I fix CVE-2004-2377?

No fix has been published for CVE-2004-2377 yet. Limit exposure of the affected software until one is available.

## Is CVE-2004-2377 being exploited?

There is no known exploitation of CVE-2004-2377 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-1999-1559](https://insights.sbomify.com/CVE-1999-1559/): Auth bypass in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-2377 and fix it if it is affected.

What it is: CVE-2004-2377 is a medium-severity denial of service vulnerability in n/a, published on 16 Aug 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2004-2377 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2004-2377/ (Markdown: https://insights.sbomify.com/CVE-2004-2377/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2004-2377
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2004-2377
- OSV: https://osv.dev/vulnerability/CVE-2004-2377

---
From sbomify Insights: https://insights.sbomify.com/CVE-2004-2377/
Summaries are generated and may contain mistakes; the official description above is the record.