Bug 236893 - CVE-2007-0243 GIF buffer overflow
Summary: CVE-2007-0243 GIF buffer overflow
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 2.1
Classification: Red Hat
Component: IBMJava2-JRE
Version: 2.1
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: ---
Assignee: Thomas Fitzsimmons
QA Contact:
URL:
Whiteboard: reported=20070417,source=internet,imp...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-04-18 10:10 UTC by Mark J. Cox
Modified: 2007-11-30 22:06 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-04-26 17:49:41 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Mark J. Cox 2007-04-18 10:10:36 UTC
+++ This bug was initially created as a clone of Bug #236892 +++

In January 2007 a flaw was found affecting the SUN JRE; "Buffer overflow in Sun
JDK and Java Runtime Environment (JRE) 5.0 Update 9 and earlier, SDK and JRE
1.4.2_12 and earlier, and SDK and JRE 1.3.1_18 and earlier allows applets to
gain privileges via a GIF image with a block with a 0 width field, which
triggers memory corruption."

On 17th April 2007 IBM updated their alerts page to note that this issue
affected the IBM JRE and was fixed in 1.4.2 SR8

Also affects RHEL4Extras, RHEL3Extras

Comment 1 Mark J. Cox 2007-04-18 10:28:37 UTC
We shipped IBM JRE version 1.3.1 with RHEL2.1; note that the IBM page
http://www-128.ibm.com/developerworks/java/jdk/alerts/ states that there is no
1.3.1 update, but "1.3.1 iFixes are available on request"

Comment 2 Thomas Fitzsimmons 2007-04-18 17:57:27 UTC
(In reply to comment #1)
> We shipped IBM JRE version 1.3.1 with RHEL2.1; note that the IBM page
> http://www-128.ibm.com/developerworks/java/jdk/alerts/ states that there is no
> 1.3.1 update, but "1.3.1 iFixes are available on request"

I've requested these updates from my IBM contact.


Comment 3 Josh Bressers 2007-04-26 17:49:41 UTC
This flaw was fixe din Java 1.3.1, which we released in RHSA-2007:0072.


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