# CVE-2007-6429: Integer overflow in n/a

> Integer overflows in X.Org Xserver allow local attackers to execute arbitrary code via crafted GetVisualInfo or pixmap requests.

- **Severity:** Critical 9.3 (`AV:N/AC:M/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:** Not needed
- **Fix available:** Yes
- **Published:** 18 Jan 2008
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-6429, GHSA-2r2g-x5x8-8vp7

## What is CVE-2007-6429?

CVE-2007-6429 is a critical vulnerability in n/a, published on 18 Jan 2008. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Multiple integer overflows in X.Org Xserver before 1.4.1 allow context-dependent attackers to execute arbitrary code via (1) a GetVisualInfo request containing a 32-bit value that is improperly used to calculate an amount of memory for allocation by the EVI extension, or (2) a request containing values related to pixmap size that are improperly used in management of shared memory by the MIT-SHM extension.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization), CWE-189

## Which versions are affected by CVE-2007-6429?

It affects 3 products.


Products: X.org Evi, X.org Mit-Shm, X.org Xserver.

## How do I fix CVE-2007-6429?

Upgrade to a fixed version.

## Is CVE-2007-6429 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-6429 and fix it if it is affected.

What it is: CVE-2007-6429 is a critical vulnerability in n/a, published on 18 Jan 2008. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-6429 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-2007-6429/ (Markdown: https://insights.sbomify.com/CVE-2007-6429/index.md)
```

## Sources

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

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