Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1410470 - (CVE-2016-10060) CVE-2016-10060 ImageMagick: Write path does not check return of fputc in magick-cli.c
CVE-2016-10060 ImageMagick: Write path does not check return of fputc in magi...
Status: CLOSED WONTFIX
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
impact=low,public=20160604,reported=2...
: Security
Depends On: 1410515
Blocks:
  Show dependency treegraph
 
Reported: 2017-01-05 10:11 EST by Andrej Nemec
Modified: 2017-01-05 11:14 EST (History)
12 users (show)

See Also:
Fixed In Version: ImageMagick 7.0.1
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-01-05 10:12:27 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Andrej Nemec 2017-01-05 10:11:21 EST
An unchecked return value vulnerability was found in ImageMagick in the magick-cli.c file. A maliciously crafted file could cause the application to crash.

Upstream bug:

https://github.com/ImageMagick/ImageMagick/issues/196

References:

http://seclists.org/oss-sec/2016/q4/758
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845196

Upstream patch:

https://github.com/ImageMagick/ImageMagick/commit/933e96f01a8c889c7bf5ffd30020e86a02a046e7
Comment 1 Andrej Nemec 2017-01-05 10:12:27 EST
Statement:

Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.
Comment 2 Andrej Nemec 2017-01-05 11:14:44 EST
Created ImageMagick tracking bugs for this issue:

Affects: fedora-all [bug 1410515]

Note You need to log in before you can comment on or make changes to this bug.