Bug 609385 - openjpeg: possible NULL deref in jp2_decode() on error code path
Summary: openjpeg: possible NULL deref in jp2_decode() on error code path
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: openjpeg
Version: 14
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Callum Lerwick
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-30 07:02 UTC by Tomas Hoger
Modified: 2010-12-02 19:15 UTC (History)
5 users (show)

Fixed In Version: openjpeg-1.3-10.fc13
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-26 01:09:39 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Tomas Hoger 2010-06-30 07:02:04 UTC
Description of problem:
openjpeg can dereference NULL pointer in jp2_decode() when trying to open malformed image.  j2k_decode() may return NULL, if that happens, error is reported to application using openjpeg (via opj_event_msg()), but the function does not return and continues processing, which leads to NULL deref when it tries to initialize image->color_space.

This was corrected upstream via:
  http://code.google.com/p/openjpeg/source/detail?r=505

Comment 1 Tomas Hoger 2010-09-30 14:15:18 UTC
Ping.

Comment 2 Bug Zapper 2010-11-03 12:42:44 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Tomas Hoger 2010-11-03 12:46:27 UTC
Affects openjpeg-1.3-9.fc14 too.

Comment 4 Fedora Update System 2010-11-23 16:40:49 UTC
openjpeg-1.3-10.fc14 has been submitted as an update for Fedora 14.
https://admin.fedoraproject.org/updates/openjpeg-1.3-10.fc14

Comment 5 Fedora Update System 2010-11-23 16:41:39 UTC
openjpeg-1.3-10.fc13 has been submitted as an update for Fedora 13.
https://admin.fedoraproject.org/updates/openjpeg-1.3-10.fc13

Comment 6 Fedora Update System 2010-11-23 17:14:29 UTC
openjpeg-1.3-10.fc12 has been submitted as an update for Fedora 12.
https://admin.fedoraproject.org/updates/openjpeg-1.3-10.fc12

Comment 7 Fedora Update System 2010-11-23 21:49:32 UTC
openjpeg-1.3-10.fc14 has been pushed to the Fedora 14 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update openjpeg'.  You can provide feedback for this update here: https://admin.fedoraproject.org/updates/openjpeg-1.3-10.fc14

Comment 8 Fedora Update System 2010-11-26 01:09:30 UTC
openjpeg-1.3-10.fc14 has been pushed to the Fedora 14 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 9 Fedora Update System 2010-12-02 19:15:44 UTC
openjpeg-1.3-10.fc13 has been pushed to the Fedora 13 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.