# CVE-2008-3910: Integer overflow in n/a

> Remote attackers can exploit an integer overflow in dns2tcp to overwrite buffers, potentially leading to code execution or service disruption.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Sep 2008
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2008-3910, GHSA-m93m-qfxm-hh2f

## What is CVE-2008-3910?

CVE-2008-3910 is a critical vulnerability in n/a, published on 4 Sep 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

dns2tcp before 0.4.1 does not properly handle negative values in a certain length field in the input argument to the (1) dns_simple_decode or (2) dns_decode function, which allows remote attackers to overwrite a buffer and have unspecified other impact.

Weakness: CWE-189

## Which versions are affected by CVE-2008-3910?

It affects 1 product.


Products: Hsc Dns2tcp.

## How do I fix CVE-2008-3910?

Upgrade to a fixed version.

## Is CVE-2008-3910 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-3910 and fix it if it is affected.

What it is: CVE-2008-3910 is a critical vulnerability in n/a, published on 4 Sep 2008. 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-2008-3910 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-2008-3910/ (Markdown: https://insights.sbomify.com/CVE-2008-3910/index.md)
```

## Sources

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

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