# CVE-2017-11637: Null dereference in n/a

> A NULL pointer dereference in GraphicsMagick allows attackers to cause a denial of service via crafted monochrome images.

- **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:** Yes
- **Published:** 26 Jul 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-11637, GHSA-jxr9-j9xp-6p4j, UBUNTU-CVE-2017-11637

## What is CVE-2017-11637?

CVE-2017-11637 is a critical vulnerability in Graphicsmagick Graphicsmagick, published on 26 Jul 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

GraphicsMagick 1.3.26 has a NULL pointer dereference in the WritePCLImage() function in coders/pcl.c during writes of monochrome images.

Weakness: CWE-476 (NULL Pointer Dereference)

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

It affects 1 product.


Products: Graphicsmagick Graphicsmagick.

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

Upgrade to a fixed version.

## Is CVE-2017-11637 being exploited?

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

## 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-11641](https://insights.sbomify.com/CVE-2017-11641/): Denial of service in n/a (critical 9.8)
- [CVE-2017-11643](https://insights.sbomify.com/CVE-2017-11643/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-11637 is a critical vulnerability in Graphicsmagick Graphicsmagick, published on 26 Jul 2017. 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-2017-11637 in the wild and no public exploit code.

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-2017-11637/ (Markdown: https://insights.sbomify.com/CVE-2017-11637/index.md)
```

## Sources

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

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