# CVE-2020-25674: Memory corruption in ImageMagick

> An out-of-bounds read in ImageMagick's PNG coder can cause a heap-buffer-overflow, leading to application crashes when processing crafted images.

- **Severity:** Medium 5.5 (`CVSS:3.1/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:** 8 Dec 2020
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2020-25674, GHSA-28m3-jxqr-cj5w, JLSEC-2026-845, UBUNTU-CVE-2020-25674

## What is CVE-2020-25674?

CVE-2020-25674 is a medium-severity memory corruption vulnerability in Debian Debian Linux, published on 8 Dec 2020. 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

WriteOnePNGImage() from coders/png.c (the PNG coder) has a for loop with an improper exit condition that can allow an out-of-bounds READ via heap-buffer-overflow. This occurs because it is possible for the colormap to have less than 256 valid values but the loop condition will loop 256 times, attempting to pass invalid colormap data to the event logger. The patch replaces the hardcoded 256 value with a call to MagickMin() to ensure the proper value is used. This could impact application availability when a specially crafted input file is processed by ImageMagick. This flaw affects ImageMagick versions prior to 7.0.8-68.

Weakness: CWE-122 (Heap-based Buffer Overflow)

## Which versions are affected by CVE-2020-25674?

It affects 2 products.


Products: Debian Debian Linux, Imagemagick Imagemagick.

## How do I fix CVE-2020-25674?

Upgrade to a fixed version.

## Is CVE-2020-25674 being exploited?

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

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-25674 and fix it if it is affected.

What it is: CVE-2020-25674 is a medium-severity memory corruption vulnerability in Debian Debian Linux, published on 8 Dec 2020. 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-2020-25674 in the wild and no public exploit code.

Affected product: Debian Debian 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-2020-25674/ (Markdown: https://insights.sbomify.com/CVE-2020-25674/index.md)
```

## Sources

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

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