Bug 917234 - CVE-2013-1802 Ruby Gem extlib: YAML parameter parsing vulnerability [epel-all]
Summary: CVE-2013-1802 Ruby Gem extlib: YAML parameter parsing vulnerability [epel-all]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: rubygem-extlib
Version: el6
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Mo Morsi
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: fst_ping=1,fst_owner=pjp
Depends On:
Blocks: CVE-2013-1802 1209124
TreeView+ depends on / blocked
 
Reported: 2013-03-02 08:54 UTC by Kurt Seifried
Modified: 2020-04-16 17:50 UTC (History)
5 users (show)

Fixed In Version: rubygem-extlib-0.9.16-1.el6
Doc Type: Release Note
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-07-08 17:11:09 UTC
Type: ---
Embargoed:
mastahnke: needinfo-
mastahnke: needinfo-


Attachments (Terms of Use)

Description Kurt Seifried 2013-03-02 08:54:48 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 Fedora EPEL.

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 creating a Bodhi update request, please use the bodhi submission link
noted 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
Bodhi notes field when available.

Please note: this issue affects multiple supported versions of Fedora EPEL.
Only one tracking bug has been filed; please ensure that it is only closed
when all affected versions are fixed.

[bug automatically created by: add-tracking-bugs]

Comment 1 Kurt Seifried 2013-03-02 08:54:53 UTC
Please use the following update submission link to create the Bodhi
request for this issue as it contains the top-level parent bug(s) as well
as this tracking bug.  This will ensure that all associated bugs get
updated when new packages are pushed to stable.

Please also ensure that the "Close bugs when update is stable" option
remains checked.

Bodhi update submission link:
https://admin.fedoraproject.org/updates/new/?type_=security&bugs=917233,917234

Comment 2 Eric Christensen 2015-04-23 13:08:38 UTC
Can an update be pushed for this package?

Comment 3 Eric Christensen 2015-06-11 18:22:44 UTC
Can this package be updated to version 0.9.16 in EL5 and EL6?

Comment 4 Mo Morsi 2015-06-15 17:42:53 UTC
I have no problem pushing an update for this but would like to send the request to epel-devel to see what the policy is regarding this & if there are any objections. Will do so later today.

Comment 5 Fedora Update System 2015-06-19 08:13:32 UTC
rubygem-extlib-0.9.16-1.el5 has been submitted as an update for Fedora EPEL 5.
https://admin.fedoraproject.org/updates/rubygem-extlib-0.9.16-1.el5

Comment 6 Fedora Update System 2015-06-19 08:15:58 UTC
rubygem-extlib-0.9.16-1.el6 has been submitted as an update for Fedora EPEL 6.
https://admin.fedoraproject.org/updates/rubygem-extlib-0.9.16-1.el6

Comment 7 Fedora Update System 2015-06-20 21:11:44 UTC
Package rubygem-extlib-0.9.16-1.el5:
* should fix your issue,
* was pushed to the Fedora EPEL 5 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=epel-testing rubygem-extlib-0.9.16-1.el5'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-EPEL-2015-6775/rubygem-extlib-0.9.16-1.el5
then log in and leave karma (feedback).

Comment 8 Fedora Update System 2015-07-08 17:11:09 UTC
rubygem-extlib-0.9.16-1.el5 has been pushed to the Fedora EPEL 5 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 9 Fedora Update System 2015-07-08 17:12:20 UTC
rubygem-extlib-0.9.16-1.el6 has been pushed to the Fedora EPEL 6 stable repository.  If problems still persist, please make note of it in this bug report.


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