# CVE-2010-1166: Memory corruption in n/a

> Remote authenticated users can trigger memory corruption in the X server Render extension, leading to denial of service or arbitrary code execution.

- **Severity:** High 7.1 (`AV:N/AC:H/Au:S/C:C/I:C/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:** 29 Apr 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-r2w8-jwh3-x7vc, RHSA-2010:0382

## What is CVE-2010-1166?

CVE-2010-1166 is a high-severity memory corruption vulnerability in n/a, published on 29 Apr 2010. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The fbComposite function in fbpict.c in the Render extension in the X server in X.Org X11R7.1 allows remote authenticated users to cause a denial of service (memory corruption and daemon crash) or possibly execute arbitrary code via a crafted request, related to an incorrect macro definition.

Weakness: CWE-189

## Which versions are affected by CVE-2010-1166?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `xorg-x11-server` | Red Hat:enterprise_linux:5::client | All versions | 0:1.1.1-48.76.el5_5.1 |
| `xorg-x11-server-Xdmx` | Red Hat:enterprise_linux:5::client | All versions | 0:1.1.1-48.76.el5_5.1 |
| `xorg-x11-server-Xephyr` | Red Hat:enterprise_linux:5::client | All versions | 0:1.1.1-48.76.el5_5.1 |
| `xorg-x11-server-Xnest` | Red Hat:enterprise_linux:5::client | All versions | 0:1.1.1-48.76.el5_5.1 |
| `xorg-x11-server-Xorg` | Red Hat:enterprise_linux:5::client | All versions | 0:1.1.1-48.76.el5_5.1 |
| `xorg-x11-server-Xvfb` | Red Hat:enterprise_linux:5::client | All versions | 0:1.1.1-48.76.el5_5.1 |
| `xorg-x11-server-Xvnc-source` | Red Hat:enterprise_linux:5::client | All versions | 0:1.1.1-48.76.el5_5.1 |
| `xorg-x11-server-debuginfo` | Red Hat:enterprise_linux:5::client | All versions | 0:1.1.1-48.76.el5_5.1 |
| `xorg-x11-server` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:1.1.1-48.76.el5_5.1 |
| `xorg-x11-server-debuginfo` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:1.1.1-48.76.el5_5.1 |
| `xorg-x11-server-sdk` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:1.1.1-48.76.el5_5.1 |
| `xorg-x11-server` | Red Hat:enterprise_linux:5::server | All versions | 0:1.1.1-48.76.el5_5.1 |
| `xorg-x11-server-Xdmx` | Red Hat:enterprise_linux:5::server | All versions | 0:1.1.1-48.76.el5_5.1 |
| `xorg-x11-server-Xephyr` | Red Hat:enterprise_linux:5::server | All versions | 0:1.1.1-48.76.el5_5.1 |
| `xorg-x11-server-Xnest` | Red Hat:enterprise_linux:5::server | All versions | 0:1.1.1-48.76.el5_5.1 |
| `xorg-x11-server-Xorg` | Red Hat:enterprise_linux:5::server | All versions | 0:1.1.1-48.76.el5_5.1 |
| `xorg-x11-server-Xvfb` | Red Hat:enterprise_linux:5::server | All versions | 0:1.1.1-48.76.el5_5.1 |
| `xorg-x11-server-Xvnc-source` | Red Hat:enterprise_linux:5::server | All versions | 0:1.1.1-48.76.el5_5.1 |
| `xorg-x11-server-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 0:1.1.1-48.76.el5_5.1 |
| `xorg-x11-server-sdk` | Red Hat:enterprise_linux:5::server | All versions | 0:1.1.1-48.76.el5_5.1 |

Products: X X.org.

## How do I fix CVE-2010-1166?

Apply the vendor's patch.

## Is CVE-2010-1166 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-1166 and fix it if it is affected.

What it is: CVE-2010-1166 is a high-severity memory corruption vulnerability in n/a, published on 29 Apr 2010. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2010-1166 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-2010-1166/ (Markdown: https://insights.sbomify.com/CVE-2010-1166/index.md)
```

## Sources

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

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