# CVE-2011-2543: Memory corruption in n/a

> Remote authenticated users can trigger a buffer overflow in Cisco Telepresence System Integrator to execute arbitrary code or cause denial of service.

- **Severity:** Critical 9.0 (`AV:N/AC:L/Au:S/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Sep 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-4288-wphc-vc7w

## What is CVE-2011-2543?

CVE-2011-2543 is a critical memory corruption vulnerability in n/a, published on 23 Sep 2011. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Buffer overflow in the cuil component in Cisco Telepresence System Integrator C Series 4.x before TC4.2.0 allows remote authenticated users to cause a denial of service (endpoint reboot or process crash) or possibly execute arbitrary code via a long location parameter to the getxml program, aka Bug ID CSCtq46496.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 4 products.


Products: Cisco Telepresence C Series Software, Cisco Telepresence Codec C40, Cisco Telepresence Codec C60, Cisco Telepresence Codec C90.

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

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

## Is CVE-2011-2543 being exploited?

There is no known exploitation of CVE-2011-2543 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-2543 and fix it if it is affected.

What it is: CVE-2011-2543 is a critical memory corruption vulnerability in n/a, published on 23 Sep 2011. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2011-2543 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-2543/ (Markdown: https://insights.sbomify.com/CVE-2011-2543/index.md)
```

## Sources

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

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