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

> Remote authenticated users can crash the X server or execute arbitrary code via crafted GLX requests in X.Org xserver.

- **Severity:** High 8.5 (`AV:N/AC:M/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:** 5 Sep 2012
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2010-4818, GHSA-c8m7-2vm3-5fjq

## What is CVE-2010-4818?

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

### Official description

The GLX extension in X.Org xserver 1.7.7 allows remote authenticated users to cause a denial of service (server crash) and possibly execute arbitrary code via (1) a crafted request that triggers a client swap in glx/glxcmdsswap.c; or (2) a crafted length or (3) a negative value in the screen field in a request to glx/glxcmds.c.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: X.org X.org.

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

Apply the vendor's patch.

## Is CVE-2010-4818 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-6102](https://insights.sbomify.com/CVE-2006-6102/): Integer overflow in n/a (critical 10.0)
- [CVE-2006-3739](https://insights.sbomify.com/CVE-2006-3739/): Integer overflow in n/a (high 7.2)
- [CVE-2006-3740](https://insights.sbomify.com/CVE-2006-3740/): Integer overflow in n/a (high 7.2)
- [CVE-2006-6101](https://insights.sbomify.com/CVE-2006-6101/): Integer overflow in n/a (medium 6.6)
- [CVE-2006-6103](https://insights.sbomify.com/CVE-2006-6103/): Integer overflow in n/a (medium 6.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2010-4818 is a high-severity memory corruption vulnerability in n/a, published on 5 Sep 2012. 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-4818 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-4818/ (Markdown: https://insights.sbomify.com/CVE-2010-4818/index.md)
```

## Sources

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

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