# CVE-2015-2778: Denial of service in n/a

> Remote attackers can crash the Quassel IRC client by sending a long CTCP query with multibyte characters, 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:** 10 Apr 2015
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2015-2778, GHSA-p62x-mmj3-75q4, UBUNTU-CVE-2015-2778

## What is CVE-2015-2778?

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

### Official description

Quassel before 0.12-rc1 uses an incorrect data-type size when splitting a message, which allows remote attackers to cause a denial of service (crash) via a long CTCP query containing only multibyte characters.

Weakness: CWE-399

## Which versions are affected by CVE-2015-2778?

It affects 1 product.


Products: Quassel-Irc Quassel.

## How do I fix CVE-2015-2778?

Upgrade to a fixed version.

## Is CVE-2015-2778 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-2779](https://insights.sbomify.com/CVE-2015-2779/): Denial of service in n/a (medium 5.0)
- [CVE-2011-3354](https://insights.sbomify.com/CVE-2011-3354/): The CtcpParser::packedReply method in core/ctcpparser.cpp in Quassel before 0.7.3 allows remote attackers to cause a denial of service (cras (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-2778 and fix it if it is affected.

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

## Sources

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

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