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

> An integer overflow in libmtp allows attackers to cause denial of service or potential code execution via a malicious USB device connection.

- **Severity:** Medium 6.8 (`CVSS:3.0/AV:P/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Jun 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-9832, GHSA-6r64-q62g-cg7v, UBUNTU-CVE-2017-9832

## What is CVE-2017-9832?

CVE-2017-9832 is a medium-severity vulnerability in n/a, published on 24 Jun 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An integer overflow vulnerability in ptp-pack.c (ptp_unpack_OPL function) of libmtp (version 1.1.12 and below) allows attackers to cause a denial of service (out-of-bounds memory access) or maybe remote code execution by inserting a mobile device into a personal computer through a USB cable.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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

It affects 1 product.


Products: Libmtp Project Libmtp.

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

Upgrade to a fixed version.

## Is CVE-2017-9832 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-9831](https://insights.sbomify.com/CVE-2017-9831/): Integer overflow in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-9832 and fix it if it is affected.

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

## Sources

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

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