# CVE-2016-5735: Integer overflow in n/a

> An integer overflow in pngquant allows remote attackers to trigger a buffer overflow via a crafted PNG file, potentially leading to code execution or denial of service.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 23 May 2017
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2016-5735, DLA-2257-1, DLA-966-1, GHSA-2326-85qm-8gr9, UBUNTU-CVE-2016-5735

## What is CVE-2016-5735?

CVE-2016-5735 is a high-severity vulnerability in n/a, published on 23 May 2017. 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 overflow in the rwpng_read_image24_libpng function in rwpng.c in pngquant 2.7.0 allows remote attackers to have unspecified impact via a crafted PNG file, which triggers a buffer overflow.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2016-5735?

It affects 1 product.


Products: Pngquant Pngquant.

## How do I fix CVE-2016-5735?

Apply the vendor's patch.

## Is CVE-2016-5735 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-5735 and fix it if it is affected.

What it is: CVE-2016-5735 is a high-severity vulnerability in n/a, published on 23 May 2017. 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-2016-5735 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-2016-5735/ (Markdown: https://insights.sbomify.com/CVE-2016-5735/index.md)
```

## Sources

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

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