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

> Remote attackers can cause a denial of service via integer overflows in potrace when processing large BMP images.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 29 Mar 2015
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2013-7437, GHSA-6fx2-mw65-fcxv, MGASA-2015-0161, UBUNTU-CVE-2013-7437, openSUSE-SU-2024:10202-1

## What is CVE-2013-7437?

CVE-2013-7437 is a medium-severity vulnerability in n/a, published on 29 Mar 2015. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Multiple integer overflows in potrace 1.11 allow remote attackers to cause a denial of service (crash) via large dimensions in a BMP image, which triggers a buffer overflow.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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

It affects 1 product.


Products: Icoasoft Potrace.

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

Upgrade to a fixed version.

## Is CVE-2013-7437 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2013-7437 is a medium-severity vulnerability in n/a, published on 29 Mar 2015. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2013-7437 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-7437/ (Markdown: https://insights.sbomify.com/CVE-2013-7437/index.md)
```

## Sources

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

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