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

> An integer overflow in QPDF's PNG filter leads to a heap-based out-of-bounds read, potentially causing crashes or information disclosure.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/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:** 13 Feb 2018
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-18185, GHSA-36w8-h6xw-wxr6, UBUNTU-CVE-2017-18185

## What is CVE-2017-18185?

CVE-2017-18185 is a medium-severity vulnerability in n/a, published on 13 Feb 2018. 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

An issue was discovered in QPDF before 7.0.0. There is a large heap-based out-of-bounds read in the Pl_Buffer::write function in Pl_Buffer.cc. It is caused by an integer overflow in the PNG filter.

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 1 product.


Products: Qpdf Project Qpdf.

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

Upgrade to a fixed version.

## Is CVE-2017-18185 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-12595](https://insights.sbomify.com/CVE-2017-12595/): Denial of service in n/a (high 7.8)
- [CVE-2022-34503](https://insights.sbomify.com/CVE-2022-34503/): Memory corruption in n/a (medium 6.5)
- [CVE-2021-36978](https://insights.sbomify.com/CVE-2021-36978/): Memory corruption in n/a (medium 5.5)
- [CVE-2015-9252](https://insights.sbomify.com/CVE-2015-9252/): Denial of service in n/a (medium 5.5)
- [CVE-2017-18183](https://insights.sbomify.com/CVE-2017-18183/): Denial of service in n/a (medium 5.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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