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. epel-6 tracking bug for rubygem-activesupport: see blocks bug list for full details of the security issue(s). [bug automatically created by: add-tracking-bugs]
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=903440,905374
Any ETA for this fix?
Upstream patches and fixed releases are disponible[0]. Fixed versions: 3.0.20 and 2.3.16. Please fix it. Links: [0] https://groups.google.com/forum/?fromgroups=#!topic/rubyonrails-security/1h2DR63ViGo
Release 4.1.0 is also available.
Can this package be upgraded to version 2.3.16 to fix this vulnerability?
Created attachment 946630 [details] Build failure on ppc64 I experience this build failure on ppc64 when applying 2-3-json-parser.patch
Created attachment 946631 [details] Diff including the patch that I tried
Any word on this being fixed?
I've now got a working scratch-build for EPEL6, and barring any objections, I'll be pushing this to EPEL 6 as an update in about 24 hours. http://koji.fedoraproject.org/koji/taskinfo?taskID=9531443
Adding jrusnack to CC, and he was helping me with this earlier today
When update is pushed bz#731451 should be closed, too.
Also I realized only later (sorry), but this is most probably not critical for el6. This critical part was because this allowed unauthenticated RCE in Rails. However, Rails stack is not in EPEL 6, just activesupport part of it.
rubygem-activesupport-2.3.18-6.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/rubygem-activesupport-2.3.18-6.el6
Package rubygem-activesupport-2.3.18-6.el6: * should fix your issue, * was pushed to the Fedora EPEL 6 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=epel-testing rubygem-activesupport-2.3.18-6.el6' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2015-6487/rubygem-activesupport-2.3.18-6.el6 then log in and leave karma (feedback).
rubygem-activesupport-2.3.18-6.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.