# CVE-2011-3287: XML external entity in n/a

> Remote attackers can cause denial of service via crafted XML documents exploiting entity expansion recursion in Cisco Jabber XCP.

- **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:** 6 Oct 2011
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-m277-38hj-98fr

## What is CVE-2011-3287?

CVE-2011-3287 is a high-severity vulnerability in n/a, published on 6 Oct 2011. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Cisco Jabber Extensible Communications Platform (aka Jabber XCP) 2.x through 5.4.x before 5.4.0.27581 and 5.8.x before 5.8.1.27561 does not properly detect recursion during entity expansion, which allows remote attackers to cause a denial of service (memory and CPU consumption, and process crash) via a crafted XML document containing a large number of nested entity references, aka Bug ID CSCtq78106, a similar issue to CVE-2003-1564.

Weakness: CWE-399

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

It affects 1 product.


Products: Cisco Jabber Extensible Communications Platform.

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

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

## Is CVE-2011-3287 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-3935](https://insights.sbomify.com/CVE-2012-3935/): Denial of service in n/a (high 7.8)
- [CVE-2013-1187](https://insights.sbomify.com/CVE-2013-1187/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2011-3287 is a high-severity vulnerability in n/a, published on 6 Oct 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-3287 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-3287/ (Markdown: https://insights.sbomify.com/CVE-2011-3287/index.md)
```

## Sources

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

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