# CVE-2022-0217: XML external entity in prosody

> Attackers can exploit XML parsing flaws in Prosody to cause denial of service or read sensitive data via entity expansion and external entity injection.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Aug 2022
- **Updated:** 2 Aug 2024
- **Also known as:** DEBIAN-CVE-2022-0217, DSA-5047-1, UBUNTU-CVE-2022-0217, openSUSE-SU-2022:0012-1, openSUSE-SU-2024:11736-1

## What is CVE-2022-0217?

CVE-2022-0217 is a high-severity vulnerability in prosody, published on 26 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

It was discovered that an internal Prosody library to load XML based on libexpat does not properly restrict the XML features allowed in parsed XML data. Given suitable attacker input, this results in expansion of recursive entity references from DTDs (CWE-776). In addition, depending on the libexpat version used, it may also allow injections using XML External Entity References (CWE-611).

Weakness: CWE-611 (Improper Restriction of XML External Entity Reference), CWE-776 (Improper Restriction of Recursive Entity References in DTDs)

## Which versions are affected by CVE-2022-0217?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `prosody` | SUSE:Package Hub 15 SP3 | All versions | 0.11.12-bp153.2.12.1 |
| `prosody` | openSUSE:Leap 15.3 | All versions | 0.11.12-bp153.2.12.1 |
| `prosody` | openSUSE:Tumbleweed | All versions | 0.11.12-1.1 |

Products: Prosody Prosody.

## How do I fix CVE-2022-0217?

Apply the vendor's patch.

## Is CVE-2022-0217 being exploited?

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

## Other vulnerabilities in prosody

- [CVE-2014-2745](https://insights.sbomify.com/CVE-2014-2745/): Denial of service in n/a (high 7.8)
- [CVE-2021-37601](https://insights.sbomify.com/CVE-2021-37601/): Information disclosure in n/a (high 7.5)
- [CVE-2026-43504](https://insights.sbomify.com/CVE-2026-43504/): Missing authorization in Prosody (medium 6.5)
- [CVE-2026-43505](https://insights.sbomify.com/CVE-2026-43505/): Missing authorization in Prosody (medium 6.5)
- [CVE-2026-43506](https://insights.sbomify.com/CVE-2026-43506/): Denial of service in Prosody (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-0217 and fix it if it is affected.

What it is: CVE-2022-0217 is a high-severity vulnerability in prosody, published on 26 Aug 2022. 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-2022-0217 in the wild and no public exploit code.

Affected product: prosody. 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-2022-0217/ (Markdown: https://insights.sbomify.com/CVE-2022-0217/index.md)
```

## Sources

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

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