CVE-2017-2587 json
A memory allocation vulnerability was found in netpbm before 10.61.
published 2018-07-27 8 y ago modified 2026-06-17 4 mo ago also EUVD-2017-11766
- cvss
- 3.3
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.3%
- EPSS 1.3% chance of exploitation in 30 days, percentile 70%
- public exploits
- 0
- none known
Summary
A memory allocation vulnerability was found in netpbm before 10.61. A maliciously crafted SVG file could cause the application to crash.
Patch / fix
- netpbm_project netpbm 10.61.00
- netpbm SLES for SAP 12 SP2, SLES for Raspberry Pi 12 SP2, SLES 12 SP2 +2 more 10.66.3-7.1
suse advisories SUSE-SU-2017:1603-1
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2017-2587 updated cvss 3.3
netpbm: Insufficient size check of memory allocation in createCanvas() function
-
Red Hat Enterprise Linux 5 netpbm Red Hat Enterprise Linux 6 netpbm, netpbm-progs Red Hat Enterprise Linux 7 netpbm, netpbm-progsaffected: no fix planned “Will not fix”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
1.27% chance of exploitation in the next 30 days, higher than 70% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 3.3 | CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L |
| NVD | 3.0 | 5.5 | CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:N/A:P |
Affected products
- Netpbm netpbm
Classification
- Weakness
-
- CWE-770 Allocation of Resources Without Limits or Throttling
References
-
securityfocus.com
/bid/96702
vdb-entry, third-party-advisory
-
bugzilla.redhat.com
/show_bug.cgi?id=CVE-2017-2587
issue-tracking, third-party-advisory
Sources
- CVE List CVE-2017-2587
- NVD CVE-2017-2587
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.