# CVE-2013-2002: Memory corruption in n/a

> A buffer overflow in libXt allows attackers to cause a crash or execute arbitrary code via crafted input to the _XtResourceConfigurationEH function.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Jun 2013
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2013-2002, GHSA-c9x5-r9w6-9jg6

## What is CVE-2013-2002?

CVE-2013-2002 is a medium-severity memory corruption vulnerability in n/a, published on 15 Jun 2013. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Buffer overflow in X.org libXt 1.1.3 and earlier allows X servers to cause a denial of service (crash) and possibly execute arbitrary code via crafted length or index values to the _XtResourceConfigurationEH function.

Weakness: CWE-189

## Which versions are affected by CVE-2013-2002?

It affects 1 product.


Products: X Libxt.

## How do I fix CVE-2013-2002?

Upgrade to a fixed version.

## Is CVE-2013-2002 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-2005](https://insights.sbomify.com/CVE-2013-2005/): Memory corruption in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-2002 and fix it if it is affected.

What it is: CVE-2013-2002 is a medium-severity memory corruption vulnerability in n/a, published on 15 Jun 2013. 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-2013-2002 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-2013-2002/ (Markdown: https://insights.sbomify.com/CVE-2013-2002/index.md)
```

## Sources

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

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