# CVE-2005-3694: Denial of service in n/a

> Remote attackers can crash the centericq client by sending short zero-length packets when peer-to-peer communications are enabled.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:N/I:N/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Nov 2005
- **Updated:** 7 Aug 2024
- **Also known as:** DSA-912-1, GHSA-g9qf-23cc-mpq5

## What is CVE-2005-3694?

CVE-2005-3694 is a high-severity denial of service vulnerability in n/a, published on 20 Nov 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

centericq 4.20.0-r3 with "Enable peer-to-peer communications" set allows remote attackers to cause a denial of service (segmentation fault and crash) via short zero-length packets, and possibly packets of length 1 or 2, as demonstrated using Nessus.

## Which versions are affected by CVE-2005-3694?

It affects 1 product.


Products: Centericq Centericq.

## How do I fix CVE-2005-3694?

Apply the vendor's patch.

## Is CVE-2005-3694 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-3694 exists.

Public exploit code:

- CenterICQ 4.20/4.5 - Packet Handling Remote Denial of Service (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-0160](https://insights.sbomify.com/CVE-2007-0160/): Memory corruption in n/a (high 7.5)
- [CVE-2005-1852](https://insights.sbomify.com/CVE-2005-1852/): Integer overflow in n/a (high 7.5)
- [CVE-2005-1914](https://insights.sbomify.com/CVE-2005-1914/): Path traversal in n/a (low 2.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-3694 and fix it if it is affected.

What it is: CVE-2005-3694 is a high-severity denial of service vulnerability in n/a, published on 20 Nov 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-3694 exists.

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-2005-3694/ (Markdown: https://insights.sbomify.com/CVE-2005-3694/index.md)
```

## Sources

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

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