# CVE-2004-0094: Integer overflow in n/a

> Remote attackers can cause denial of service or execute arbitrary code via integer signedness errors in the XFree86 GLX extension.

- **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:** 1 Sep 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-g3xh-7cc5-g3q9

## What is CVE-2004-0094?

CVE-2004-0094 is a high-severity vulnerability in n/a, published on 1 Sep 2004. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Integer signedness errors in XFree86 4.1.0 allow remote attackers to cause a denial of service and possibly execute arbitrary code when using the GLX extension and Direct Rendering Infrastructure (DRI).

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

It affects 1 product.


Products: Xfree86 Project X11r6.

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

Upgrade to a fixed version.

## Is CVE-2004-0094 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2002-1510](https://insights.sbomify.com/CVE-2002-1510/): Auth bypass in n/a (critical 10.0)
- [CVE-2004-0093](https://insights.sbomify.com/CVE-2004-0093/): Memory corruption in n/a (high 7.5)
- [CVE-2001-1086](https://insights.sbomify.com/CVE-2001-1086/): Weak cryptography in n/a (high 7.5)
- [CVE-2003-0063](https://insights.sbomify.com/CVE-2003-0063/): Command injection in n/a (high 7.3)
- [CVE-2002-1472](https://insights.sbomify.com/CVE-2002-1472/): Privilege escalation in n/a (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2004-0094 is a high-severity vulnerability in n/a, published on 1 Sep 2004. 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-2004-0094 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-2004-0094/ (Markdown: https://insights.sbomify.com/CVE-2004-0094/index.md)
```

## Sources

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

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