# CVE-2005-2487: Denial of service in n/a

> Attackers can cause denial of service and loss of connectivity on Sun McData switches via network broadcast storms.

- **Severity:** Low 2.1 (`AV:L/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:** 7 Aug 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-m8px-c66j-46j6

## What is CVE-2005-2487?

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

### Official description

Unknown vulnerability in Sun McData switches and directors 4300, 4500, 6064, and 6140 before E/OS 6.0.0 may allow attackers to cause a denial of service (connectivity and array access loss) via a network broadcast storm.

## Which versions are affected by CVE-2005-2487?

It affects 4 products.


Products: Mcdata Intrepid 6064 Director Switch, Mcdata Intrepid 6140 Director Switch, Mcdata Sphereon 4300 Fabric Switch, Mcdata Sphereon 4500 Fabric Switch.

## How do I fix CVE-2005-2487?

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

## Is CVE-2005-2487 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-2487 and fix it if it is affected.

What it is: CVE-2005-2487 is a low-severity denial of service vulnerability in n/a, published on 7 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-2005-2487 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-2005-2487/ (Markdown: https://insights.sbomify.com/CVE-2005-2487/index.md)
```

## Sources

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

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