Bug 486355 - (CVE-2009-0040) CVE-2009-0040 libpng arbitrary free() flaw
CVE-2009-0040 libpng arbitrary free() flaw
Status: CLOSED ERRATA
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
low Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
http://213.203.218.125/l/li/libpng/li...
source=vendorsec,reported=20090212,pu...
: Security
Depends On: 487164 487165 487166 487167 487168 487169 487170 487171 487172 537849 802164
Blocks:
  Show dependency treegraph
 
Reported: 2009-02-19 09:01 EST by Josh Bressers
Modified: 2015-07-27 04:37 EDT (History)
13 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2011-09-30 19:41:38 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)
Upstream advisory for posterity (1.65 KB, text/plain)
2009-02-19 09:02 EST, Josh Bressers
no flags Details
Upstream patch to fix the issue (2.63 KB, patch)
2009-02-20 19:59 EST, Vincent Danen
no flags Details | Diff

  None (edit)
Description Josh Bressers 2009-02-19 09:01:24 EST
A flaw was discovered in libpng that could result in libpng trying to free() random memory if certain unlikely error conditions occur.  To quote the libpng advisory:

    If the application runs out of memory during the
    loop, some of the element pointers will be uninitialized.
    Libpng will then longjmp to a cleanup process that
    attempts to free all of the elements in the array,
    including the uninitialized ones.  This behavior
    could be forced by a malevolent input.
Comment 1 Josh Bressers 2009-02-19 09:02:33 EST
Created attachment 332560 [details]
Upstream advisory for posterity
Comment 2 Vincent Danen 2009-02-20 19:59:16 EST
Created attachment 332781 [details]
Upstream patch to fix the issue
Comment 9 Fedora Update System 2009-02-26 04:02:41 EST
mingw32-libpng-1.2.35-1.fc10 has been submitted as an update for Fedora 10.
http://admin.fedoraproject.org/updates/mingw32-libpng-1.2.35-1.fc10
Comment 10 Richard W.M. Jones 2009-02-26 04:03:21 EST
Thanks for the heads up on this.  I have rebuilt
the mingw32-libpng package in Rawhide, F-10 and EL-5.
Comment 11 Paul Howarth 2009-02-26 04:50:00 EST
Upstream release 1.0.43 addresses this issue for libpng10.

Rawhide is already updated, and updates for F-9 and F-10 are currently in updates-testing.

https://admin.fedoraproject.org/updates/F9/FEDORA-2009-2045
https://admin.fedoraproject.org/updates/F10/FEDORA-2009-1976
Comment 12 Fedora Update System 2009-02-26 10:33:16 EST
libpng-1.2.35-1.fc10 has been pushed to the Fedora 10 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 13 Fedora Update System 2009-02-26 10:34:32 EST
libpng-1.2.35-1.fc9 has been pushed to the Fedora 9 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 14 Fedora Update System 2009-02-26 10:35:27 EST
mingw32-libpng-1.2.35-1.fc10 has been pushed to the Fedora 10 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 22 Fedora Update System 2009-03-09 18:47:32 EDT
libpng10-1.0.43-1.fc9 has been pushed to the Fedora 9 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 23 Fedora Update System 2009-03-09 19:11:15 EDT
libpng10-1.0.43-1.fc10 has been pushed to the Fedora 10 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 24 Fedora Update System 2009-03-20 21:26:13 EDT
thunderbird-2.0.0.21-1.fc10 has been pushed to the Fedora 10 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 25 Fedora Update System 2009-03-20 21:27:17 EDT
thunderbird-2.0.0.21-1.fc9 has been pushed to the Fedora 9 stable repository.  If problems still persist, please make note of it in this bug report.

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