# CVE-2007-2437: Denial of service in n/a

> Remote authenticated users can crash the X server via crafted values in XRender functions, causing a denial of service.

- **Severity:** Medium 5.5 (`AV:A/AC:L/Au:S/C:N/I:N/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 May 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-2437, GHSA-j82p-p2jg-jj2f

## What is CVE-2007-2437?

CVE-2007-2437 is a medium-severity denial of service vulnerability in n/a, published on 2 May 2007. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The X render (Xrender) extension in X.org X Window System 7.0, 7.1, and 7.2, with Xserver 1.3.0 and earlier, allows remote authenticated users to cause a denial of service (daemon crash) via crafted values to the (1) XRenderCompositeTrapezoids and (2) XRenderAddTraps functions, which trigger a divide-by-zero error.

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

It affects 2 products.


Products: X.org X Window System, X.org Xserver.

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

Upgrade to a fixed version.

## Is CVE-2007-2437 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-2437 exists.

Public exploit code:

- X.Org X Window System Xserver 1.3 - XRender Extension Divide by Zero Denial of Service (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-2437 is a medium-severity denial of service vulnerability in n/a, published on 2 May 2007. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-2437 exists.

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-2437/ (Markdown: https://insights.sbomify.com/CVE-2007-2437/index.md)
```

## Sources

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

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