Bug 1002714 (CVE-2013-1438, CVE-2013-1439) - CVE-2013-1438 CVE-2013-1439 LibRaw: multiple denial of service flaws
Summary: CVE-2013-1438 CVE-2013-1439 LibRaw: multiple denial of service flaws
Keywords:
Status: CLOSED WONTFIX
Alias: CVE-2013-1438, CVE-2013-1439
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1002717 1002718 1011752 1011753 1014011 1063126
Blocks: 1002723
TreeView+ depends on / blocked
 
Reported: 2013-08-29 18:57 UTC by Vincent Danen
Modified: 2021-02-17 07:23 UTC (History)
8 users (show)

Fixed In Version: LibRaw 0.15.4
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-08-22 03:24:48 UTC
Embargoed:


Attachments (Terms of Use)

Description Vincent Danen 2013-08-29 18:57:54 UTC
Raphael Geissert reported two denial of service flaws in LibRaw [1]:

CVE-2013-1438:

Specially crafted photo files may trigger a division by zero, an
infinite loop, or a null pointer dereference in libraw leading to
denial of service in applications using the library.
These vulnerabilities appear to originate in dcraw and as such any
program or library based on it is affected. To name a few confirmed
applications: dcraw, ufraw. Other affected software: shotwell,
darktable, and libkdcraw (Qt-style interface to libraw, using embedded
copy) which is used by digikam.

Google Picasa apparently uses dcraw/ufraw so it might be affected.
dcraw's homepage has a list of applications that possibly still use
it:
http://cybercom.net/~dcoffin/dcraw/

Affected versions of libraw: confirmed: 0.8-0.15.3; but it is likely
that all versions are affected.

Fixed in: libraw 0.15.4

CVE-2013-1439:

Specially crafted photo files may trigger a series of conditions in
which a null pointer is dereferenced leading to denial of service in
applications using the library. These three vulnerabilities are
in/related to the 'faster LJPEG decoder', which upstream states was
introduced in LibRaw 0.13 and support for which is going to be dropped
in 0.16.

Affected versions of libraw: 0.13.x-0.15.x

Fixed in: libraw 0.15.4

Patches:
0.15.x:
https://github.com/LibRaw/LibRaw/commit/11909cc59e712e09b508dda729b99aeaac2b29ad
Future 0.16.x:
https://github.com/LibRaw/LibRaw/commit/9ae25d8c3a6bfb40c582538193264f74c9b93bc0

(upstream decided to commit all fixes in a single commit. The missing
changes in the patch for 0.16 are the ones that correspond to
CVE-2013-4139. I.e. 0.16 patchset is CVE-2013-1438, while the 0.15
patchset is CVE-2013-4138 + CVE-2013-4139.)

Upstream states that there will be backported fixes for the 0.14
branch but there won't be any new release and "[they] should use
0.14-stable branch from github repo".

Comment 2 Vincent Danen 2013-08-29 19:00:08 UTC
Created LibRaw tracking bugs for this issue:

Affects: fedora-all [bug 1002717]

Comment 3 Huzaifa S. Sidhpurwala 2013-09-25 05:14:06 UTC
Created dcraw tracking bugs for this issue:

Affects: fedora-all [bug 1011753]

Comment 5 Nils Philippsen 2013-09-25 13:34:12 UTC
I've checked out the commits fixing the issue(s) in LibRaw, and it seems as if only CVE-2013-1438 applies to dcraw, as CVE-2013-1439 affects the "faster LJPEG decoder" which is only in LibRaw, and there only in versions 0.13.x-0.15.x. Do you concur?

Should we have a separate bug for this issue in ufraw, or shall I handle it in the context of dcraw?

Comment 7 Huzaifa S. Sidhpurwala 2013-10-01 09:12:44 UTC
Created ufraw tracking bugs for this issue:

Affects: fedora-all [bug 1014011]

Comment 8 Fedora Update System 2013-12-16 22:59:58 UTC
dcraw-9.19-4.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 9 Fedora Update System 2013-12-16 23:02:17 UTC
ufraw-0.19.2-10.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 10 Fedora Update System 2013-12-16 23:04:54 UTC
dcraw-9.19-4.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 11 Fedora Update System 2013-12-16 23:05:35 UTC
ufraw-0.19.2-10.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 12 Fedora Update System 2013-12-17 19:11:59 UTC
ufraw-0.19.2-10.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 13 Fedora Update System 2013-12-17 19:15:45 UTC
dcraw-9.19-4.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 14 Debarshi Ray 2014-01-08 10:16:43 UTC
This is the patch for the 0.14-stable series: https://github.com/LibRaw/LibRaw/commit/c4e374ea6c979a7d1d968f5082b7d0ea8cd27202

Comment 15 Murray McAllister 2014-02-10 05:00:31 UTC
According to https://bugs.mageia.org/show_bug.cgi?id=12693 and https://bugs.mageia.org/show_bug.cgi?id=11149#c14 the version of rawtherapee in Fedora is vulnerable to CVE-2013-1438

Comment 16 Murray McAllister 2014-02-10 05:06:30 UTC
Created rawtherapee tracking bugs for this issue:

Affects: fedora-all [bug 1063126]

Comment 17 Vincent Danen 2015-08-22 03:24:35 UTC
Statement:

Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.


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