# CVE-2008-3157: Denial of service in n/a

> Attackers can cause denial of service in Nortel SIP Multimedia PC Client by exhausting resources through unlimited concurrent sessions.

- **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:** 11 Jul 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-4m2p-89qj-vmq6

## What is CVE-2008-3157?

CVE-2008-3157 is a medium-severity denial of service vulnerability in n/a, published on 11 Jul 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Nortel SIP Multimedia PC Client 4.x MCS5100 and MCS5200 does not limit the number of concurrent sessions, which allows attackers to cause a denial of service (resource consumption) via a large number of sessions.

Weakness: CWE-399

## Which versions are affected by CVE-2008-3157?

It affects 1 product.


Products: Nortel Sip Multimedia Pc Client.

## How do I fix CVE-2008-3157?

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

## Is CVE-2008-3157 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-3157 and fix it if it is affected.

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

## Sources

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

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