Red Hat Bugzilla – Bug 1466749
CVE-2017-9224 CVE-2017-9225 CVE-2017-9226 CVE-2017-9227 CVE-2017-9228 CVE-2017-9229 ruby: various flaws [fedora-all]
Last modified: 2017-09-27 07:16:08 EDT
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
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:
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. 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.
Use the following template to for the 'fedpkg update' request to submit an
update 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.
# bugfix, security, enhancement, newpackage (required)
# testing, stable
# Bug numbers: 1234,9876
# Description of your update
notes=Security fix for [PUT CVEs HERE]
# Enable request automation based on the stable/unstable karma thresholds
# Automatically close bugs when this marked as stable
# Suggest that users restart after update
Additionally, you may opt to use the bodhi web interface to submit updates:
So would you check the updates already pushed 20 days ago?
(In reply to Mamoru TASAKA from comment #2)
> So would you check the updates already pushed 20 days ago?
Oops... not for this component, sorry.
Ruby is not vulnerable according to upstream:
All cases are rendered harmless by the Ruby interpreter,
then pure Ruby script can not make any attack.
But, Onigumo APIs are also published in Ruby, so we should
fix these issue, of course.
In Ruby these issues are not serious incidents, and in any case
we usually not treat such issues as vulnerabilities.
I think these should be treated as normal bugs.
See the detailed reasoning in tracking bugs ...
Closing this now as NOTABUG.
*** Bug 1457774 has been marked as a duplicate of this bug. ***