Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1543597 - Rebase to 0.19.2
Summary: Rebase to 0.19.2
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: LibRaw
Version: 7.7
Hardware: All
OS: Unspecified
unspecified
urgent
Target Milestone: rc
: ---
Assignee: Debarshi Ray
QA Contact: Desktop QE
URL:
Whiteboard:
: 1557172 1557186 1557203 1575861 1575863 1610705 1611636 1613945 1663163 (view as bug list)
Depends On:
Blocks: CVE-2018-5800 CVE-2018-5801 CVE-2018-5802 CVE-2018-10528 CVE-2018-10529 CVE-2018-5805 CVE-2018-5813 CVE-2018-5810 1652700 CVE-2018-5819 CVE-2018-5818
TreeView+ depends on / blocked
 
Reported: 2018-02-08 19:22 UTC by James Boyle
Modified: 2019-09-24 12:46 UTC (History)
10 users (show)

Fixed In Version: LibRaw-0.19.1-1.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-06 12:37:16 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:2044 0 None None None 2019-08-06 12:38:31 UTC

Description James Boyle 2018-02-08 19:22:24 UTC
The version of LibRaw included with RHEL 7 (0.14.8-5) is out of date.  It contains multiple critical vulnerabilities:
CVE-2017-14608
CVE-2017-14265
CVE-2017-13735
CVE-2017-6887
CVE-2017-6886
CVE-2017-6889

Refer to the NIST NVD for more information about the flaws.

Upstream source from libraw.org is available, but it appears neither has the newer source been built nor patches backported.

Here is the last entry from the LibRaw package from RHEL 7:
* Fri Jan 24 2014 Daniel Mach <dmach> - 0.14.8-5.20120830git98d925
- Mass rebuild 2014-01-24

Comment 2 Kalev Lember 2018-05-15 19:28:31 UTC
Should we maybe rebase LibRaw to 0.18.11 as part of the 7.6 desktop rebase?

Comment 3 Debarshi Ray 2018-05-16 14:49:51 UTC
I'd like to, but it involves an ABI break. So we need to check how this might affect EPEL.

Comment 4 Debarshi Ray 2018-11-22 15:57:54 UTC
Let's go ahead. My understanding is that EPEL packages can be expected to be rebuilt against the new soname. I think I recently saw an email fly by to that effect, but I can't find it at the moment. If there are issues with customers relying on the earlier soname, then I am happy to provide a compatibility package.

Comment 5 Debarshi Ray 2018-11-22 16:03:24 UTC
(In reply to Kalev Lember from comment #2)
> Should we maybe rebase LibRaw to 0.18.11 as part of the 7.6 desktop rebase?

The current supported series is 0.19.x, so we should rebase to that now. That's also what we have in RHEL 8.

Comment 7 Debarshi Ray 2018-11-22 16:44:20 UTC
... and will enable support for a whole host of new cameras.

Comment 8 Debarshi Ray 2018-12-17 12:03:53 UTC
Built LibRaw-0.19.1-1.el7:
https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=19536039

Comment 9 Debarshi Ray 2018-12-17 12:05:49 UTC
*** Bug 1575861 has been marked as a duplicate of this bug. ***

Comment 10 Debarshi Ray 2018-12-17 12:06:19 UTC
*** Bug 1610705 has been marked as a duplicate of this bug. ***

Comment 11 Debarshi Ray 2018-12-17 12:06:43 UTC
*** Bug 1613945 has been marked as a duplicate of this bug. ***

Comment 12 Debarshi Ray 2018-12-17 12:07:03 UTC
*** Bug 1557172 has been marked as a duplicate of this bug. ***

Comment 13 Debarshi Ray 2018-12-17 12:07:42 UTC
*** Bug 1557186 has been marked as a duplicate of this bug. ***

Comment 14 Debarshi Ray 2018-12-17 12:08:04 UTC
*** Bug 1557203 has been marked as a duplicate of this bug. ***

Comment 15 Debarshi Ray 2018-12-17 12:08:34 UTC
*** Bug 1575863 has been marked as a duplicate of this bug. ***

Comment 16 Debarshi Ray 2018-12-17 12:09:46 UTC
*** Bug 1611636 has been marked as a duplicate of this bug. ***

Comment 19 Debarshi Ray 2019-02-01 13:57:22 UTC
*** Bug 1663163 has been marked as a duplicate of this bug. ***

Comment 20 Debarshi Ray 2019-02-01 14:03:25 UTC
*** Bug 1663170 has been marked as a duplicate of this bug. ***

Comment 24 errata-xmlrpc 2019-08-06 12:37:16 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:2044


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