Bug 1520227 (CVE-2017-16938) - CVE-2017-16938 optipng: global buffer overflow in gifread.c:LZWReadByte when parsing malicious GIF
Summary: CVE-2017-16938 optipng: global buffer overflow in gifread.c:LZWReadByte when ...
Keywords:
Status: CLOSED WONTFIX
Alias: CVE-2017-16938
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1520230
Blocks: 1520229
TreeView+ depends on / blocked
 
Reported: 2017-12-04 05:04 UTC by Sam Fowler
Modified: 2021-02-17 01:10 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
An invalid memory write flaw was found in the way OptiPNG handles processing of GIF files. This flaw could potentially be used to crash the OptiPNG program by tricking it into processing crafted GIF files.
Clone Of:
Environment:
Last Closed: 2018-01-05 08:14:45 UTC
Embargoed:

Attachments (Terms of Use)

Description Sam Fowler 2017-12-04 05:04:11 UTC 
A global buffer overflow in OptiPNG 0.7.6 allows remote attackers to cause a denial-of-service attack with a maliciously crafted GIF format file, related to an uncontrolled loop in the LZWReadByte function of the gifread.c file.

References:

https://nvd.nist.gov/vuln/detail/CVE-2017-16938
https://bugs.debian.org/878839
https://bugs.gentoo.org/639690
https://bugs.mageia.org/show_bug.cgi?id=22099
https://bugzilla.suse.com/show_bug.cgi?id=1069774
https://sourceforge.net/p/optipng/bugs/69/
https://sourceforge.net/p/optipng/bugs/_discuss/thread/10e27bff/63db/attachment/optipng-076-sfbug-69.patch
Comment 1 Sam Fowler 2017-12-04 05:22:11 UTC 
Created optipng tracking bugs for this issue:

Affects: fedora-all [bug 1520230]
Comment 3 Dhiru Kholia 2018-01-05 08:17:30 UTC 
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/.
Note You need to log in before you can comment on or make changes to this bug.