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

> An integer overflow in apng2gif leads to a heap-based buffer over-read, potentially causing crashes or information disclosure.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Mar 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-6960, DLA-2165-1, DLA-981-1, GHSA-hqw9-4vmr-235r, UBUNTU-CVE-2017-6960, USN-4513-1

## What is CVE-2017-6960?

CVE-2017-6960 is a high-severity vulnerability in Canonical Ubuntu Linux, published on 17 Mar 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in apng2gif 1.7. There is an integer overflow resulting in a heap-based buffer over-read, related to the load_apng function and the imagesize variable.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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

It affects 3 products.


Products: Apng2gif Project Apng2gif, Canonical Ubuntu Linux, Debian Debian Linux.

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

Apply the vendor's patch.

## Is CVE-2017-6960 being exploited?

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

## Other vulnerabilities in Canonical Ubuntu Linux

- [CVE-2017-6962](https://insights.sbomify.com/CVE-2017-6962/): Integer overflow in n/a (high 7.5)
- [CVE-2017-6961](https://insights.sbomify.com/CVE-2017-6961/): Denial of service in n/a (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-6960 is a high-severity vulnerability in Canonical Ubuntu Linux, published on 17 Mar 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-6960 in the wild and no public exploit code.

Affected product: Canonical Ubuntu Linux. 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-6960/ (Markdown: https://insights.sbomify.com/CVE-2017-6960/index.md)
```

## Sources

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

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