# CVE-2013-2003: Integer overflow in n/a

> An integer overflow in libXcursor allows attackers to trigger buffer overflows, potentially leading to code execution or denial of service.

- **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-2003, DSA-2681-1, GHSA-m53r-v9v7-fx9r, openSUSE-SU-2024:10176-1

## What is CVE-2013-2003?

CVE-2013-2003 is a medium-severity 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

Integer overflow in X.org libXcursor 1.1.13 and earlier allows X servers to trigger allocation of insufficient memory and a buffer overflow via vectors related to the _XcursorFileHeaderCreate function.

Weakness: CWE-189

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

It affects 1 product.


Products: X Libxcursor.

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

Apply the vendor's patch.

## Is CVE-2013-2003 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2013-2003 is a medium-severity 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-2003 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-2003/ (Markdown: https://insights.sbomify.com/CVE-2013-2003/index.md)
```

## Sources

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

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