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

> Local attackers can execute arbitrary code via crafted AFM files exploiting an integer overflow in the X.Org X server.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 13 Sep 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2006-3739, GHSA-h3pc-gf82-7xhp

## What is CVE-2006-3739?

CVE-2006-3739 is a high-severity vulnerability in n/a, published on 13 Sep 2006. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Integer overflow in the CIDAFM function in X.Org 6.8.2 and XFree86 X server allows local users to execute arbitrary code via crafted Adobe Font Metrics (AFM) files with a modified number of character metrics (StartCharMetrics), which leads to a heap-based buffer overflow.

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

It affects 2 products.


Products: X.org X.org, Xfree86 Project Xfree86 X.

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

Apply the vendor's patch.

## Is CVE-2006-3739 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-6102](https://insights.sbomify.com/CVE-2006-6102/): Integer overflow in n/a (critical 10.0)
- [CVE-2010-4818](https://insights.sbomify.com/CVE-2010-4818/): Memory corruption in n/a (high 8.5)
- [CVE-2006-3740](https://insights.sbomify.com/CVE-2006-3740/): Integer overflow in n/a (high 7.2)
- [CVE-2006-6101](https://insights.sbomify.com/CVE-2006-6101/): Integer overflow in n/a (medium 6.6)
- [CVE-2006-6103](https://insights.sbomify.com/CVE-2006-6103/): Integer overflow in n/a (medium 6.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-3739 is a high-severity vulnerability in n/a, published on 13 Sep 2006. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2006-3739 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-3739/ (Markdown: https://insights.sbomify.com/CVE-2006-3739/index.md)
```

## Sources

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

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