# CVE-2017-2586: Null dereference in netpbm

> A maliciously crafted SVG file can cause a crash in the Netpbm library due to a null pointer dereference.

- **Severity:** Low 3.3 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L`)
- **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:** 27 Jul 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-g2rm-3545-j3gr

## What is CVE-2017-2586?

CVE-2017-2586 is a low-severity vulnerability in netpbm, published on 27 Jul 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

A null pointer dereference vulnerability was found in netpbm before 10.61. A maliciously crafted SVG file could cause the application to crash.

Weakness: CWE-476 (NULL Pointer Dereference)

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

It affects 1 product.


Products: Netpbm Project Netpbm.

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

Upgrade to a fixed version.

## Is CVE-2017-2586 being exploited?

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

## Other vulnerabilities in netpbm

- [CVE-2018-8975](https://insights.sbomify.com/CVE-2018-8975/): Memory corruption in n/a (medium 5.5)
- [CVE-2017-2580](https://insights.sbomify.com/CVE-2017-2580/): Memory corruption in netpbm (medium 4.5)
- [CVE-2017-2581](https://insights.sbomify.com/CVE-2017-2581/): Memory corruption in netpbm (medium 4.5)
- [CVE-2017-2579](https://insights.sbomify.com/CVE-2017-2579/): Memory corruption in netpbm (low 3.3)
- [CVE-2017-2587](https://insights.sbomify.com/CVE-2017-2587/): Denial of service in netpbm (low 3.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-2586 is a low-severity vulnerability in netpbm, published on 27 Jul 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-2586 in the wild and no public exploit code.

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

## Sources

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

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