# CVE-2011-2577: Denial of service in n/a

> Remote attackers can crash Cisco TelePresence endpoints by sending crafted SIP packets, requiring a software upgrade to mitigate.

- **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:** 31 Aug 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-gcc6-6jc3-v432

## What is CVE-2011-2577?

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

### Official description

Unspecified vulnerability in Cisco TelePresence C Series Endpoints, E/EX Personal Video units, and MXP Series Codecs, when using software versions before TC 4.0.0 or F9.1, allows remote attackers to cause a denial of service (crash) via a crafted SIP packet to port 5060 or 5061, aka Bug ID CSCtq46500.

## Which versions are affected by CVE-2011-2577?

It affects 11 products.


Products: Cisco Telepresence 6000 Mxp, Cisco Telepresence 9000 Mxp, Cisco Telepresence C Series Software, Cisco Telepresence Codec C40, Cisco Telepresence Codec C60, Cisco Telepresence Codec C90, Cisco Telepresence E20, Cisco Telepresence E20 Software, Cisco Telepresence Ex60, Cisco Telepresence Ex90, Cisco Telepresence Mxp Software.

## How do I fix CVE-2011-2577?

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

## Is CVE-2011-2577 being exploited?

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

Public exploit code:

- Cisco TelePresence SOS-11-010 - Multiple Vulnerabilities (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-2577 and fix it if it is affected.

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

## Sources

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

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