Bug 150503 - CAN-2005-0664 buffer overflow in libexif
Summary: CAN-2005-0664 buffer overflow in libexif
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: libexif
Version: 3.0
Hardware: All
OS: Linux
medium
low
Target Milestone: ---
Assignee: Marco Pesenti Gritti
QA Contact:
URL:
Whiteboard: impact=low,public=20040303,source=ven...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-03-07 20:43 UTC by Josh Bressers
Modified: 2007-11-30 22:07 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-03-21 18:22:21 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2005:300 0 normal SHIPPED_LIVE Low: libexif security update 2005-03-21 05:00:00 UTC

Description Josh Bressers 2005-03-07 20:43:03 UTC
Ubuntu alerted vendor-sec to a buffer overflow reported to their BTS regarding
processing exif headers with libexif.

See:
https://bugzilla.ubuntulinux.org/show_bug.cgi?id=7152
http://sourceforge.net/tracker/index.php?func=detail&aid=1158402&group_id=12272&atid=312272

The sourceforge bug suggests this is only a DoS.

Comment 1 Marco Pesenti Gritti 2005-03-09 11:36:19 UTC
I released FC2/FC3 updates and I filed an errata request. Do I need to file a QA
request? I'm not sure what ask to test since there are not testcases of the
issue available...

Comment 2 Mark J. Cox 2005-03-14 11:53:34 UTC
This is a crash only of a user application, therefore this is low
severity.

Comment 3 Mark J. Cox 2005-03-21 18:22:22 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2005-300.html



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