# CVE-2006-2971: Integer overflow in n/a

> Remote attackers can crash the 0verkill game server by sending a small UDP 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:** 12 Jun 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-fv6q-r6mc-4p4j

## What is CVE-2006-2971?

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

### Official description

Integer overflow in the recv_packet function in 0verkill 0.16 allows remote attackers to cause a denial of service (daemon crash) via a UDP packet with fewer than 12 bytes, which results in a long length value to the crc32 function.

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

It affects 1 product.


Products: Overkill Overkill.

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

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

## Is CVE-2006-2971 being exploited?

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

Public exploit code:

- 0verkill 0.16 - ASCII-ART Game Remote Integer Overflow Crash (PoC) (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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