libpng 1.6.15 is already in the tree. Upstream considers this a security release, it fixes a possible out of bounds memory access when an app is executed with a different libpng version than it was compiled against. (I was somewhat indirectly involved in the discovery of this issue while fuzzing graphicsmagick.) It is likely a minor issue and I'm not sure it would get a CVE, however I still think this deserves fast-track stabilization just to be sure. Probably not worth a GLSA though. From upstream homepage: Virtually all libpng versions through 1.6.14, 1.5.19, 1.4.13, 1.2.51, and 1.0.61, respectively, have an out-of-bounds memory access in png_user_version_check(). It is unclear whether this could lead to an actual exploit. The bug is fixed in versions 1.6.15, 1.5.20, etc., released on 20 November 2014.
@maintainers: Is this package ready for stabilization?
(In reply to Kristian Fiskerstrand from comment #1) > @maintainers: Is this package ready for stabilization? Go for it.
Arches please stabilize: =media-libs/libpng-1.2.52 Stable targets: amd64 x86 =media-libs/libpng-1.5.20 Stable targets: amd64 x86 =media-libs/libpng-1.6.15 Stable targets: alpha amd64 arm hppa ia64 ppc ppc64 sparc x86
amd64 stable
x86 stable
Stable for HPPA.
ia64 stable
*** Bug 532630 has been marked as a duplicate of this bug. ***
arm stable
alpha stable
ppc stable
ppc64 stable
sparc stable. Maintainer(s), please cleanup. Security, please add it to the existing request, or file a new one.
This issue was resolved and addressed in GLSA 201502-10 at http://security.gentoo.org/glsa/glsa-201502-10.xml by GLSA coordinator Kristian Fiskerstrand (K_F).
=media-libs/libpng-1.2.51 is still in the tree, so cleanup wasn't done properly.
(In reply to Jeroen Roovers from comment #16) > =media-libs/libpng-1.2.51 is still in the tree, so cleanup wasn't done > properly. Thanks. Setting cleanup state again
Cleanup was completed.