# CVE-2004-2410: Null dereference in n/a

> Attackers can cause a denial of service in Samhain via a null pointer dereference in sh_hash_compdata.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Aug 2005
- **Updated:** 16 Sep 2024
- **Also known as:** DEBIAN-CVE-2004-2410, GHSA-jgvh-63v4-rgq5

## What is CVE-2004-2410?

CVE-2004-2410 is a low-severity vulnerability in n/a, published on 18 Aug 2005. 

### Official description

Unknown vulnerability in sh_hash_compdata for Samhain 1.8.9 through 2.0.1 might allow attackers to cause a denial of service (null pointer dereference).

## Which versions are affected by CVE-2004-2410?

It affects 1 product.


Products: Samhain Labs Samhain.

## How do I fix CVE-2004-2410?

Upgrade to a fixed version.

## Is CVE-2004-2410 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-4810](https://insights.sbomify.com/CVE-2009-4810/): Auth bypass in n/a (high 7.5)
- [CVE-2004-2409](https://insights.sbomify.com/CVE-2004-2409/): Memory corruption in n/a (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-2410 and fix it if it is affected.

What it is: CVE-2004-2410 is a low-severity vulnerability in n/a, published on 18 Aug 2005. 
Exploitation: There is no known exploitation of CVE-2004-2410 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-2004-2410/ (Markdown: https://insights.sbomify.com/CVE-2004-2410/index.md)
```

## Sources

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

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