Bug 979295 - ruby: CVE-2013-4073 ruby: hostname check bypassing vulnerability in SSL client [fedora-all]
Summary: ruby: CVE-2013-4073 ruby: hostname check bypassing vulnerability in SSL clien...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: ruby
Version: 18
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeroen van Meeuwen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: component:ruby
Depends On:
Blocks: CVE-2013-4073
TreeView+ depends on / blocked
 
Reported: 2013-06-28 07:53 UTC by Kurt Seifried
Modified: 2013-07-16 01:35 UTC (History)
7 users (show)

Fixed In Version: ruby-2.0.0.247-14.fc19
Doc Type: Release Note
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-16 01:35:55 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Kurt Seifried 2013-06-28 07:53:06 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.

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.
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-06-28 07:53:18 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=979251,979295

Comment 2 Fedora Update System 2013-07-01 04:03:09 UTC
ruby-1.9.3.448-31.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/ruby-1.9.3.448-31.fc18

Comment 3 Fedora Update System 2013-07-01 04:04:06 UTC
ruby-1.9.3.448-31.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/ruby-1.9.3.448-31.fc17

Comment 4 Fedora Update System 2013-07-01 14:03:07 UTC
ruby-2.0.0.247-9.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/ruby-2.0.0.247-9.fc19

Comment 5 Fedora Update System 2013-07-02 00:30:47 UTC
Package ruby-2.0.0.247-9.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing ruby-2.0.0.247-9.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-12118/ruby-2.0.0.247-9.fc19
then log in and leave karma (feedback).

Comment 6 Fedora Update System 2013-07-09 11:06:50 UTC
ruby-2.0.0.247-12.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/ruby-2.0.0.247-12.fc19

Comment 7 Fedora Update System 2013-07-11 02:28:05 UTC
ruby-1.9.3.448-31.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 8 Fedora Update System 2013-07-11 02:33:12 UTC
ruby-1.9.3.448-31.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 9 Fedora Update System 2013-07-16 01:35:55 UTC
ruby-2.0.0.247-14.fc19 has been pushed to the Fedora 19 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.