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

> Remote attackers can cause a denial of service in Prosody XMPP server via infinite loop triggered by invalid JSON data.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Jun 2011
- **Updated:** 16 Sep 2024
- **Also known as:** DEBIAN-CVE-2011-2532, GHSA-mq6h-jh39-cjg8

## What is CVE-2011-2532?

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

### Official description

The json.decode function in util/json.lua in Prosody 0.8.x before 0.8.1 might allow remote attackers to cause a denial of service (infinite loop) via invalid JSON data, as demonstrated by truncated data.

Weakness: CWE-399

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

It affects 1 product.


Products: Prosody Prosody.

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

Upgrade to a fixed version.

## Is CVE-2011-2532 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-2745](https://insights.sbomify.com/CVE-2014-2745/): Denial of service in n/a (high 7.8)
- [CVE-2022-0217](https://insights.sbomify.com/CVE-2022-0217/): XML external entity in prosody (high 7.5)
- [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)

## Fix prompt for AI coding agents

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

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

## Sources

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

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