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

> An integer underflow in AutoTrace allows attackers to trigger a buffer overflow via a crafted BMP file, 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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 9 Dec 2013
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2013-1953, GHSA-j9fj-j92c-8fqr, MGASA-2013-0195, UBUNTU-CVE-2013-1953

## What is CVE-2013-1953?

CVE-2013-1953 is a medium-severity vulnerability in Autotrace Project Autotrace, published on 9 Dec 2013. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Integer underflow in the input_bmp_reader function in input-bmp.c in AutoTrace 0.31.1 allows context-dependent attackers to have an unspecified impact via a small value in the biSize field in the header of a BMP file, which triggers a buffer overflow.

Weakness: CWE-189

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

It affects 1 product.


Products: Autotrace Project Autotrace.

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

Upgrade to a fixed version.

## Is CVE-2013-1953 being exploited?

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

## Other vulnerabilities in Autotrace Project Autotrace

- [CVE-2017-9151](https://insights.sbomify.com/CVE-2017-9151/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-9152](https://insights.sbomify.com/CVE-2017-9152/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-9153](https://insights.sbomify.com/CVE-2017-9153/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-9160](https://insights.sbomify.com/CVE-2017-9160/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-9161](https://insights.sbomify.com/CVE-2017-9161/): Integer overflow in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-1953 is a medium-severity vulnerability in Autotrace Project Autotrace, published on 9 Dec 2013. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2013-1953 in the wild and no public exploit code.

Affected product: Autotrace Project Autotrace. 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-1953/ (Markdown: https://insights.sbomify.com/CVE-2013-1953/index.md)
```

## Sources

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

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