# CVE-2017-9162: Integer overflow in n/a

> An integer overflow in AutoTrace library can cause a crash, requiring a patch to prevent denial of service.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 May 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-56gc-475p-h7cc, UBUNTU-CVE-2017-9162

## What is CVE-2017-9162?

CVE-2017-9162 is a critical vulnerability in Autotrace Project Autotrace, published on 23 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

libautotrace.a in AutoTrace 0.31.1 has a "cannot be represented in type int" issue in autotrace.c:191:2.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2017-9162?

It affects 1 product.


Products: Autotrace Project Autotrace.

## How do I fix CVE-2017-9162?

No fix has been published for CVE-2017-9162 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-9162 being exploited?

There is no known exploitation of CVE-2017-9162 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-2017-9162 and fix it if it is affected.

What it is: CVE-2017-9162 is a critical vulnerability in Autotrace Project Autotrace, published on 23 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-9162 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-2017-9162/ (Markdown: https://insights.sbomify.com/CVE-2017-9162/index.md)
```

## Sources

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

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