Bug 1610469 (CVE-2018-5807) - CVE-2018-5807 LibRaw: out-of-bounds read in samsung_load_raw in internal/dcraw_common.cpp
Summary: CVE-2018-5807 LibRaw: out-of-bounds read in samsung_load_raw in internal/dcra...
Keywords:
Status: CLOSED NOTABUG
Alias: CVE-2018-5807
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: 1610470 1610471 1610472 1610473
Blocks: 1610488
TreeView+ depends on / blocked
 
Reported: 2018-07-31 17:15 UTC by Laura Pardo
Modified: 2021-02-16 23:51 UTC (History)
7 users (show)

Fixed In Version: LibRaw 0.18.9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-08-08 13:48:37 UTC
Embargoed:


Attachments (Terms of Use)

Description Laura Pardo 2018-07-31 17:15:03 UTC
A flaw was found in LibRaw versions before 0.18.9. An error within the samsung_load_raw() function (internal/dcraw_common.cpp) can be exploited to cause an out-of-bounds read memory access and subsequently cause a crash.


References:
https://secuniaresearch.flexerasoftware.com/secunia_research/2018-10/

Comment 1 Laura Pardo 2018-07-31 17:15:53 UTC
Created LibRaw tracking bugs for this issue:

Affects: epel-6 [bug 1610472]
Affects: fedora-all [bug 1610470]


Created mingw-LibRaw tracking bugs for this issue:

Affects: fedora-all [bug 1610471]

Comment 3 Riccardo Schirone 2018-08-08 08:46:06 UTC
Upstream patch:
https://github.com/LibRaw/LibRaw/commit/c9d8143eba4ff397163665e2119c6c5d7db54c55

Comment 4 Riccardo Schirone 2018-08-08 13:48:37 UTC
In RHEL 7, the code in dcraw_common.cpp, generated from dcraw.cpp, does not contain the `samsung_load_raw` function and it does not support the TIFF tag 40976, related to Samsung.

Comment 5 Riccardo Schirone 2018-08-08 13:48:45 UTC
Statement:

This issue did not affect the versions of LibRaw as shipped with Red Hat Enterprise Linux 7 as they did not include the vulnerable code.


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