# CVE-2006-0048: Denial of service in n/a

> Remote attackers can cause a denial of service in tcpick via fragmented packets with invalid headers, potentially leading to a segmentation fault.

- **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:** Yes
- **Published:** 26 Apr 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2006-0048, GHSA-jmgw-fgrg-vw35

## What is CVE-2006-0048?

CVE-2006-0048 is a medium-severity denial of service vulnerability in n/a, published on 26 Apr 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Francesco Stablum tcpick 0.2.1 allows remote attackers to cause a denial of service (segmentation fault) via certain fragmented packets, possibly involving invalid headers and an attacker-controlled payload length.  NOTE: this issue might be a buffer overflow or overread.

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

It affects 1 product.


Products: Francesco Stablum Tcpick.

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

Upgrade to a fixed version.

## Is CVE-2006-0048 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2006-0048 is a medium-severity denial of service vulnerability in n/a, published on 26 Apr 2006. 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-2006-0048 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-2006-0048/ (Markdown: https://insights.sbomify.com/CVE-2006-0048/index.md)
```

## Sources

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

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