# CVE-2018-7264: Memory corruption in n/a

> Remote attackers can execute arbitrary code by exploiting out-of-bounds write errors in the Pictview image processing library within ActivePDF Toolkit.

- **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:** 28 Feb 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-fch6-4rhp-4hqm

## What is CVE-2018-7264?

CVE-2018-7264 is a critical memory corruption vulnerability in n/a, published on 28 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Pictview image processing library embedded in the ActivePDF toolkit through 2018.1.0.18321 is prone to multiple out of bounds write and sign errors, allowing a remote attacker to execute arbitrary code on vulnerable applications using the ActivePDF Toolkit to process untrusted images.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2018-7264?

It affects 1 product.


Products: Activepdf Activepdf Toolkit.

## How do I fix CVE-2018-7264?

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

## Is CVE-2018-7264 being exploited?

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

Public exploit code:

- ActivePDF Toolkit < 8.1.0.19023 - Multiple Memory Corruptions (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-7264 and fix it if it is affected.

What it is: CVE-2018-7264 is a critical memory corruption vulnerability in n/a, published on 28 Feb 2018. 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-2018-7264 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-2018-7264/ (Markdown: https://insights.sbomify.com/CVE-2018-7264/index.md)
```

## Sources

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

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