This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes
Bug 152921 - CAN-2005-0664 libexif buffer overflow
CAN-2005-0664 libexif buffer overflow
Status: CLOSED NOTABUG
Product: Fedora Legacy
Classification: Retired
Component: Package request (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Fedora Legacy Bugs
http://cve.mitre.org/cgi-bin/cvename....
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-03-10 16:04 EST by Marc Deslauriers
Modified: 2008-05-01 11:38 EDT (History)
0 users

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


Attachments (Terms of Use)

  None (edit)
Description David Lawrence 2005-03-30 18:32:15 EST
Buffer overflow in the EXIF library (libexif) 0.6.9 does not properly validate
the structure of the EXIF tags, which allows remote attackers to cause a denial
of service (application crash) and possibly execute arbitrary code via an image
with a crafted EXIF tag.

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2005-0664
https://bugzilla.redhat.com/beta/show_bug.cgi?id=150503
https://bugzilla.ubuntulinux.org/show_bug.cgi?id=7152



------- Additional Comments From marcdeslauriers@videotron.ca 2005-03-10 16:07:19 ----

Whoops...no libexif in our stuff...



------- Bug moved to this database by dkl@redhat.com 2005-03-30 18:32 -------

This bug previously known as bug 2452 at https://bugzilla.fedora.us/
https://bugzilla.fedora.us/show_bug.cgi?id=2452
Originally filed under the Fedora Legacy product and Package request component.

Unknown priority P2. Setting to default priority "normal".
Unknown platform PC. Setting to default platform "All".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.


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