# CVE-2010-0305: Denial of service in n/a

> Remote attackers can crash the ejabberd XMPP server by sending a large volume of client-to-server messages, causing a denial of service.

- **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:** 3 Feb 2010
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2010-0305, DSA-2033-1, GHSA-32wp-p7j2-grh2

## What is CVE-2010-0305?

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

### Official description

ejabberd_c2s.erl in ejabberd before 2.1.3 allows remote attackers to cause a denial of service (daemon crash) via a large number of c2s (aka client2server) messages that trigger a queue overload.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2010-0305?

It affects 1 product.


Products: Process-One Ejabberd.

## How do I fix CVE-2010-0305?

Upgrade to a fixed version.

## Is CVE-2010-0305 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-0903](https://insights.sbomify.com/CVE-2007-0903/): Other in n/a (critical 10.0)
- [CVE-2014-8760](https://insights.sbomify.com/CVE-2014-8760/): Security feature bypass in n/a (medium 5.0)
- [CVE-2011-1753](https://insights.sbomify.com/CVE-2011-1753/): Denial of service in n/a (medium 5.0)
- [CVE-2013-6169](https://insights.sbomify.com/CVE-2013-6169/): Weak cryptography in n/a (medium 4.3)
- [CVE-2009-0934](https://insights.sbomify.com/CVE-2009-0934/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-0305 and fix it if it is affected.

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

## Sources

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

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