A cross-site scripting (XSS) flaw was found in the way 'select' helper method of the Ruby on Rails performed HTML escaping of 'select' HTML tag options, when the tags were created manually. In this case, the select tag values might end up unescaped. A remote-attacker could provide a specially-crafted input to Ruby on Rails application, using select tags this way, which potentially resulted into arbitrary HTML or webscript execution. References: [1] http://weblog.rubyonrails.org/2012/3/1/ann-rails-3-0-12-has-been-released [2] http://groups.google.com/group/rubyonrails-security/browse_thread/thread/9da0c515a6c4664 [3] https://bugs.gentoo.org/show_bug.cgi?id=406547 Proposed upstream patches: [4] http://groups.google.com/group/rubyonrails-security/attach/6fca4f5c47705488/3-0-select_options.patch?part=3 (against v3.0 branch) [5] http://groups.google.com/group/rubyonrails-security/attach/6fca4f5c47705488/3-1-select_options.patch?part=4 (against v3.1 branch) [6] http://groups.google.com/group/rubyonrails-security/attach/6fca4f5c47705488/3-2-select_options.patch?part=5 (against v3.2 branch)
This issue affects the versions of the rubygem-actionpack package, as shipped with Fedora release of 15 and 16. Please schedule an update. -- This issue did NOT affect the version of the rubygem-action package, as shipped with Fedora EPEL 5.
Created rubygem-actionpack tracking bugs for this issue Affects: fedora-all [bug 799279]
CVE request: [7] http://www.openwall.com/lists/oss-security/2012/03/02/6
Added CVE as per http://www.openwall.com/lists/oss-security/2012/03/03/1
rubygem-actionpack-3.0.11-2.fc17, rubygem-activesupport-3.0.11-3.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
rubygem-actionpack-3.0.10-3.fc16, rubygem-activesupport-3.0.10-2.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
rubygem-actionpack-3.0.5-6.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.