# CVE-2006-3913: Memory corruption in n/a

> Remote attackers can trigger a buffer overflow in Freeciv servers to cause crashes or execute arbitrary code via malformed packets.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/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:** 28 Jul 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2006-3913, DSA-1142-1, GHSA-jh72-rhv6-r272

## What is CVE-2006-3913?

CVE-2006-3913 is a high-severity memory corruption vulnerability in n/a, published on 28 Jul 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer overflow in Freeciv 2.1.0-beta1 and earlier, and SVN 15 Jul 2006 and earlier, allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via a (1) negative chunk_length or a (2) large chunk->offset value in a PACKET_PLAYER_ATTRIBUTE_CHUNK packet in the generic_handle_player_attribute_chunk function in common/packets.c, and (3) a large packet->length value in the handle_unit_orders function in server/unithand.c.

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

It affects 1 product.


Products: Freeciv Freeciv.

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

Upgrade to a fixed version.

## Is CVE-2006-3913 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-2445](https://insights.sbomify.com/CVE-2010-2445/): Code injection in n/a (critical 10.0)
- [CVE-2022-39047](https://insights.sbomify.com/CVE-2022-39047/): Memory corruption in n/a (high 8.8)
- [CVE-2012-6083](https://insights.sbomify.com/CVE-2012-6083/): Denial of service in freeciv (high 7.5)
- [CVE-2006-0047](https://insights.sbomify.com/CVE-2006-0047/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-3913 is a high-severity memory corruption vulnerability in n/a, published on 28 Jul 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-3913 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-3913/ (Markdown: https://insights.sbomify.com/CVE-2006-3913/index.md)
```

## Sources

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

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