Bug 1412634 - CVE-2016-1514 CVE-2016-1515 libebml: various flaws [epel-all]
Summary: CVE-2016-1514 CVE-2016-1515 libebml: various flaws [epel-all]
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: libebml
Version: el6
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
Assignee: Hans de Goede
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: CVE-2016-1514 CVE-2016-1515
TreeView+ depends on / blocked
 
Reported: 2017-01-12 13:57 UTC by Andrej Nemec
Modified: 2017-01-12 22:57 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Release Note
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-12 22:57:44 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Andrej Nemec 2017-01-12 13:57:40 UTC
This is an automatically created tracking bug!  It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of epel-all.

For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.

For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs

When submitting as an update, use the fedpkg template provided in the next
comment(s).  This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.

Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.

NOTE: this issue affects multiple supported versions of Fedora EPEL. While
only one tracking bug has been filed, please correct all affected versions
at the same time.  If you need to fix the versions independent of each
other, you may clone this bug as appropriate.

Comment 1 Dominik 'Rathann' Mierzejewski 2017-01-12 21:47:56 UTC
EPEL7 is not vulnerable (1.3.3 contains fixes for both), so marking this as EL6.

Again, why did you file this a year after the TALOS report?

Comment 2 Dominik 'Rathann' Mierzejewski 2017-01-12 22:57:44 UTC
Our EL6 package has backported fixes for this already. I believe these are duplicates of CVE-2015-8790 and CVE-2015-8789.


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