# CVE-2008-2953: Null dereference in n/a

> Remote attackers can crash the Linux DC++ client by sending partial file list requests, 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:** No
- **Published:** 1 Jul 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-w847-ffvp-553c

## What is CVE-2008-2953?

CVE-2008-2953 is a medium-severity vulnerability in n/a, published on 1 Jul 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Linux DC++ (linuxdcpp) before 0.707 allows remote attackers to cause a denial of service (crash) via "partial file list requests" that trigger a NULL pointer dereference.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2008-2953?

It affects 1 product.


Products: Linux Direct Connect.

## How do I fix CVE-2008-2953?

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

## Is CVE-2008-2953 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-2954](https://insights.sbomify.com/CVE-2008-2954/): Denial of service in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-2953 and fix it if it is affected.

What it is: CVE-2008-2953 is a medium-severity vulnerability in n/a, published on 1 Jul 2008. 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-2008-2953 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-2008-2953/ (Markdown: https://insights.sbomify.com/CVE-2008-2953/index.md)
```

## Sources

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

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