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

> Remote attackers can cause denial of service in Microsoft Communicator by sending numerous SIP INVITE requests, leading to excessive memory consumption.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Nov 2008
- **Updated:** 15 Oct 2024
- **Also known as:** GHSA-3j45-2pqx-6qf3

## What is CVE-2008-5180?

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

### Official description

Microsoft Communicator, and Communicator in Microsoft Office 2010 beta, allows remote attackers to cause a denial of service (memory consumption) via a large number of SIP INVITE requests, which trigger the creation of many sessions.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

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

It affects 1 product.


Products: Microsoft Office Communicator.

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

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

## Is CVE-2008-5180 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-5180 exists.

Public exploit code:

- Microsoft Office - Communicator 'SIP' Remote Denial of Service (exploitdb)
- Microsoft Office 2010 Beta - Communicator SIP Denial of Service (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2008-5181](https://insights.sbomify.com/CVE-2008-5181/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-5180 is a medium-severity denial of service vulnerability in n/a, published on 20 Nov 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-5180 exists.

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-5180/ (Markdown: https://insights.sbomify.com/CVE-2008-5180/index.md)
```

## Sources

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

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