dbcve.org
NetpbmApplication · Netpbm Project

CVE-2017-2586

MEDIUM · 5.5 CVSS v3.0 Published 2018-07-27
Fix available
A fix is available. Upgrade to 10.61.00 or later.
See remediation →
58/100
Remediation priority · Elevated
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A null pointer dereference vulnerability exists in netpbm versions prior to 10.61 when parsing SVG files. When a specially crafted SVG file is processed, the application dereferences a null pointer, causing a crash.

MitigationUpdate netpbm to version 10.61 or later to obtain the patch. If immediate patching is not possible, restrict processing to trusted SVG files from known sources.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
NetpbmApplication
Affected:< 10.61.00

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify netpbm is installed
    Run 'which netpbm' or check for netpbm binaries in common paths like /usr/bin/netpbm, /usr/local/bin/netpbm, or use package managers: 'dpkg -l | grep netpbm' (Debian) or 'rpm -qa | grep netpbm' (RHEL)
    Affected if netpbm is not installed on the system
  2. Determine the installed netpbm version
    Run 'netpbm --version' or 'ppmtogif --version' or check the package version using your system package manager
    Affected if the version number returned is less than 10.61.00 (e.g., 10.60, 10.55, etc.)
  3. Check if SVG processing tools are available
    Look for netpbm SVG-related utilities such as 'svgtoppm', 'svg2png', or any tool that converts SVG files. Use 'ls /usr/bin/*svg*' or 'which svgtoppm'
    Affected if SVG conversion tools from netpbm are present on the system
  4. Confirm the vulnerable code path can be triggered
    Attempt to process a malformed SVG file using netpbm SVG tools (e.g., 'svgtoppm malformed.svg output.ppm') and observe if the application crashes or segfaults
    Affected if processing a malformed SVG file causes a null pointer dereference crash

Your environment is affected if netpbm is installed with a version prior to 10.61.00 AND you use netpbm tools to process SVG files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 10.61.00 or later
Fixed in 10.61.00
Interim mitigation

Update netpbm to version 10.61 or later to obtain the patch. If immediate patching is not possible, restrict processing to trusted SVG files from known sources.

Fix this in Netpbm Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-2586 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-2586 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data