# CVE-2002-2306: Denial of service in n/a

> Remote attackers can cause denial of service via CPU consumption by sending large messages to KaZaA Media Desktop.

- **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:** No
- **Published:** 19 Oct 2007
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-794j-jvx4-wrgc

## What is CVE-2002-2306?

CVE-2002-2306 is a high-severity denial of service vulnerability in n/a, published on 19 Oct 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Sharman Networks KaZaA Media Desktop 1.7.1 allows remote attackers to cause a denial of service (CPU consumption) by sending several large messages.

Weakness: CWE-399

## Which versions are affected by CVE-2002-2306?

It affects 1 product.


Products: Kazaa Kazaa Media Desktop.

## How do I fix CVE-2002-2306?

No fix has been published for CVE-2002-2306 yet. Limit exposure of the affected software until one is available.

## Is CVE-2002-2306 being exploited?

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

Public exploit code:

- KaZaA Media Desktop 1.7.1 - Large Message Denial of Service (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2003-1395](https://insights.sbomify.com/CVE-2003-1395/): Memory corruption in n/a (critical 9.0)
- [CVE-2003-1283](https://insights.sbomify.com/CVE-2003-1283/): Security feature bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-2306 and fix it if it is affected.

What it is: CVE-2002-2306 is a high-severity denial of service vulnerability in n/a, published on 19 Oct 2007. 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-2002-2306 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-2002-2306/ (Markdown: https://insights.sbomify.com/CVE-2002-2306/index.md)
```

## Sources

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

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