# CVE-2020-21679: Memory corruption in n/a

> Remote attackers can cause denial of service in GraphicsMagick by converting a crafted image file to PCX format due to a buffer overflow.

- **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:** 22 Aug 2023
- **Updated:** 7 Oct 2024
- **Also known as:** DEBIAN-CVE-2020-21679, GHSA-5c8v-qg3w-p36f, OESA-2023-1811, OESA-2023-1817, OESA-2023-1818, OESA-2023-1819, OESA-2023-1820, SUSE-SU-2023:3739-1, SUSE-SU-2023:3792-1, UBUNTU-CVE-2020-21679

## What is CVE-2020-21679?

CVE-2020-21679 is a medium-severity memory corruption vulnerability in Graphicsmagick Graphicsmagick, published on 22 Aug 2023. 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

Buffer Overflow vulnerability in WritePCXImage function in pcx.c in GraphicsMagick 1.4 allows remote attackers to cause a denial of service via converting of crafted image file to pcx format.

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

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ImageMagick` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 6.8.8.1-71.198.1 |
| `ImageMagick` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 6.8.8.1-71.198.1 |
| `ImageMagick` | SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 6.8.8.1-71.198.1 |
| `ImageMagick` | SUSE:Linux Enterprise Workstation Extension 12 SP5 | All versions | 6.8.8.1-71.198.1 |
| `ImageMagick` | openSUSE:Leap 15.4 | All versions | 7.0.7.34-150200.10.54.1 |

Products: Graphicsmagick Graphicsmagick.

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

Apply the vendor's patch.

## Is CVE-2020-21679 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-21679 exists.

## Other vulnerabilities in Graphicsmagick Graphicsmagick

- [CVE-2008-6071](https://insights.sbomify.com/CVE-2008-6071/): Memory corruption in n/a (critical 10.0)
- [CVE-2019-11005](https://insights.sbomify.com/CVE-2019-11005/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-11636](https://insights.sbomify.com/CVE-2017-11636/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-11637](https://insights.sbomify.com/CVE-2017-11637/): Null dereference in n/a (critical 9.8)
- [CVE-2017-11641](https://insights.sbomify.com/CVE-2017-11641/): Denial of service in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-21679 is a medium-severity memory corruption vulnerability in Graphicsmagick Graphicsmagick, published on 22 Aug 2023. 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-21679 exists.

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

## Sources

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

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