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

> Remote attackers can crash the Raydium network library by sending a specific packet, 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:** 16 May 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-vc7m-qp78-6qrv

## What is CVE-2006-2410?

CVE-2006-2410 is a medium-severity vulnerability in n/a, published on 16 May 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

raydium_network_netcall_exec function in network.c in Raydium SVN revision 312 and earlier allows remote attackers to cause a denial of service (application crash) via a packet of type 0xFF, which causes a null dereference.

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

It affects 1 product.


Products: Raydium Raydium.

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

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

## Is CVE-2006-2410 being exploited?

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

Public exploit code:

- raydium svn 309 - Multiple Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2006-2408](https://insights.sbomify.com/CVE-2006-2408/): Memory corruption in n/a (high 7.5)
- [CVE-2006-2411](https://insights.sbomify.com/CVE-2006-2411/): Memory corruption in n/a (high 7.5)
- [CVE-2006-2412](https://insights.sbomify.com/CVE-2006-2412/): Denial of service in n/a (medium 5.0)
- [CVE-2006-2409](https://insights.sbomify.com/CVE-2006-2409/): Code injection in n/a (medium 4.6)

## Fix prompt for AI coding agents

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

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

## Sources

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

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