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

> Remote attackers can cause a denial of service by hanging the media card in Nortel CS 1000 VoIP systems.

- **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 stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 May 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-h847-vwmq-pp6m

## What is CVE-2007-2886?

CVE-2007-2886 is a medium-severity denial of service vulnerability in n/a, published on 30 May 2007. It can be exploited over the network, with no action from the victim.

### Official description

Unspecified vulnerability in the Nortel CS 1000 M media card in Enterprise VoIP-Core-CS 1000E, 1000M, and 1000S 04.50W before 20070523 in Meridian/CS 1000 allows remote attackers to cause a denial of service (card hang) via unspecified vectors.

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

It affects 1 product.


Products: Nortel Communications Server.

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

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

## Is CVE-2007-2886 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2007-2886 is a medium-severity denial of service vulnerability in n/a, published on 30 May 2007. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-2886 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-2886/ (Markdown: https://insights.sbomify.com/CVE-2007-2886/index.md)
```

## Sources

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

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