Bug 958198 (CVE-2015-8472) - VUL-1: CVE-2015-8472: libpng*: incomplete fix for callers on png_set_PLTE
Summary: VUL-1: CVE-2015-8472: libpng*: incomplete fix for callers on png_set_PLTE
Status: RESOLVED DUPLICATE of bug 954980
Alias: CVE-2015-8472
Product: SUSE Security Incidents
Classification: Novell Products
Component: Incidents (show other bugs)
Version: unspecified
Hardware: Other Other
: P4 - Low : Normal
Target Milestone: ---
Assignee: Security Team bot
QA Contact: Security Team bot
URL:
Whiteboard: CVSSv2:SUSE:CVE-2015-8472:4.3:(AV:L/A...
Keywords:
Depends on:
Blocks:
 
Reported: 2015-12-07 15:05 UTC by Marcus Meissner
Modified: 2019-04-24 14:45 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marcus Meissner 2015-12-07 15:05:17 UTC
via oss-sec

On Thu, Nov 12, 2015 at 1:26 PM, Glenn Randers-Pehrson <glennrp@gmail.com>
wrote:

> I request a CVE for a vulnerability in libpng, all versions, in the
> png_set_PLTE/png_get_PLTE functions.  These functions failed to check for
> an out-of-range palette when reading or writing PNG files with a bit_depth
> less than 8.  Some applications might read the bit depth from the IHDR
> chunk and allocate memory for a 2^N entry palette, while libpng can return
> a palette with up to 256 entries even when the bit depth is less than 8.
>
> libpng versions 1.6.19, 1.5.24, 1.4.17, 1.2.54, and 1.0.64 were released
> today (12 November 2015) to fix this vulnerability.  See
> libpng.sourceforge.net
>

The patch was incomplete.  While it defended against the potential overrun
while reading PNG files, it did not detect a potential overrun by
applications using png_set_PLTE directly.  Libpng versions 1.6.20, 1.5.25,
1.4.18, 1.2.55, and 1.0.65 which were released today, December 3, 2015, fix
this remaining problem.

The PNG Development Group has not yet been made aware of any application
that is actually vulnerable to CVE-2015-8126. The original "crash" obtained
by fuzzing optipng had triggered an assert() that probably should have been
a warning; no out-of-bounds read occurs in optipng.

Regards

Glenn Randers-Pehrson
libpng custodian
Comment 1 Marcus Meissner 2015-12-07 15:07:20 UTC
From mitre: 

Use CVE-2015-8472 for this remaining problem that existed
in 1.6.19, 1.5.24, 1.4.17, 1.2.54, and 1.0.64.
Comment 2 Marcus Meissner 2015-12-07 15:08:44 UTC
see bug CVE-2015-8126.
Comment 3 Petr Gajdos 2015-12-07 15:18:56 UTC
From what I know, this is not regression, but incompleteness.

Packages with the fix for CVE-2015-8472 was already submitted on Thursday 4th.
Comment 4 Swamp Workflow Management 2015-12-07 23:00:13 UTC
bugbot adjusting priority
Comment 5 Marcus Meissner 2016-08-29 06:38:05 UTC
fixes were tracked via releases in bug 954980

*** This bug has been marked as a duplicate of bug 954980 ***