# CVE-2004-0106: Memory corruption in n/a

> Attackers can execute arbitrary code or escalate privileges by tricking users into opening malicious font files in XFree86.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 16 Feb 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-x923-wg49-3cpx

## What is CVE-2004-0106?

CVE-2004-0106 is a high-severity memory corruption vulnerability in Openbsd Openbsd, published on 16 Feb 2004. 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

Multiple unknown vulnerabilities in XFree86 4.1.0 to 4.3.0, related to improper handling of font files, a different set of vulnerabilities than CVE-2004-0083 and CVE-2004-0084.

## Which versions are affected by CVE-2004-0106?

It affects 2 products.


Products: Openbsd Openbsd, Xfree86 Project X11r6.

## How do I fix CVE-2004-0106?

Upgrade to a fixed version.

## Is CVE-2004-0106 being exploited?

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

## Other vulnerabilities in Openbsd Openbsd

- [CVE-2007-1365](https://insights.sbomify.com/CVE-2007-1365/): Memory corruption in n/a (critical 10.0)
- [CVE-2004-0220](https://insights.sbomify.com/CVE-2004-0220/): Integer overflow in n/a (critical 10.0)
- [CVE-2004-0083](https://insights.sbomify.com/CVE-2004-0083/): Memory corruption in n/a (critical 10.0)
- [CVE-2004-0084](https://insights.sbomify.com/CVE-2004-0084/): Memory corruption in n/a (critical 10.0)
- [CVE-2001-0284](https://insights.sbomify.com/CVE-2001-0284/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-0106 and fix it if it is affected.

What it is: CVE-2004-0106 is a high-severity memory corruption vulnerability in Openbsd Openbsd, published on 16 Feb 2004. 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-2004-0106 in the wild and no public exploit code.

Affected product: Openbsd Openbsd. 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-2004-0106/ (Markdown: https://insights.sbomify.com/CVE-2004-0106/index.md)
```

## Sources

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

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