# CVE-2007-5591: Denial of service in n/a

> Remote attackers can cause telephony outages by flooding packets to ELAN ports on Nortel CS1000 signaling servers.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:N/I:N/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Oct 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-pwh2-rcv8-v6g8

## What is CVE-2007-5591?

CVE-2007-5591 is a high-severity denial of service vulnerability in n/a, published on 19 Oct 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The CS1000 signaling server in Nortel Enterprise VoIP-Core-CS 1000M Chassis/Cabinet, Enterprise VoIP-Core-CS 1000E and 1000S, Meridian-Core-Option 11C Chassis and Cabinet, and Meridian-Core-Option 51C, 61C, and 81C allows remote attackers to cause a denial of service (telephony application outage) via a flood of packets to Embedded LAN (ELAN) ports.

## Which versions are affected by CVE-2007-5591?

It affects 5 products.


Products: Nortel Meridian Option 11c, Nortel Meridian Option 51c, Nortel Meridian Option 61c, Nortel Meridian Option 81c, Nortel Voip-Core-Cs.

## How do I fix CVE-2007-5591?

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

## Is CVE-2007-5591 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-5591 and fix it if it is affected.

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

## Sources

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

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