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

> Authenticated remote attackers can read arbitrary files or cause denial of service via XML external entity injection in DJabberd.

- **Severity:** Medium 5.5 (`AV:N/AC:L/Au:S/C:P/I:N/A:P`)
- **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:** 22 Jun 2011
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-r2jf-vq9h-96p6

## What is CVE-2011-2206?

CVE-2011-2206 is a medium-severity vulnerability in n/a, published on 22 Jun 2011. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

XMLParser.pm in DJabberd before 0.85 allows remote authenticated users to read arbitrary files, and possibly send HTTP requests to intranet servers or cause a denial of service (CPU and memory consumption), via an XML external entity declaration in conjunction with an entity reference, a different vulnerability than CVE-2011-1757.

Weakness: CWE-399

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

It affects 1 product.


Products: Brad Fitzpatrick Djabberd.

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

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

## Is CVE-2011-2206 being exploited?

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

## Other vulnerabilities in n/a

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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