Bug 1789102
Summary: | CVE-2019-16782 rubygem-rack: hijack sessions by using timing attacks targeting the session id [epel-6] | ||
---|---|---|---|
Product: | [Fedora] Fedora EPEL | Reporter: | Guilherme de Almeida Suckevicz <gsuckevi> |
Component: | rubygem-rack | Assignee: | Steve Traylen <steve.traylen> |
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | el6 | CC: | gp, jaruga, mo, ruby-packagers-sig, steve.traylen, strzibny, vondruch |
Target Milestone: | --- | Keywords: | Security, SecurityTracking |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | No Doc Update | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-11-30 15:39:48 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1789100 |
Description
Guilherme de Almeida Suckevicz
2020-01-08 18:15:16 UTC
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) type=security # low, medium, high, urgent (required) severity=medium # testing, stable request=testing # Bug numbers: 1234,9876 bugs=1789100,1789102 # Description of your update notes=Security fix for [PUT CVEs HERE] # Enable request automation based on the stable/unstable karma thresholds autokarma=True stable_karma=3 unstable_karma=-3 # Automatically close bugs when this marked as stable close_bugs=True # Suggest that users restart after update suggest_reboot=False ====== Additionally, you may opt to use the bodhi web interface to submit updates: https://bodhi.fedoraproject.org/updates/new URL of a successful rack 1.6.12 scratch build: https://koji.fedoraproject.org/koji/taskinfo?taskID=40397926 I do not know if it is useful for EPEL6. The output of the check session is: + ruby -Ilib -e 'require '\''rubygems'\''; load "test/gemloader.rb" ' Cannot load bacon >= 0 + for f in 'test/*.rb' + ruby -Ilib -e 'require '\''rubygems'\''; load "test/spec_auth_basic.rb" ' ./test/spec_auth_basic.rb:5: undefined method `describe' for main:Object (NoMethodError) from -e:1:in `load' from -e:1 + FAILED_TESTS=' test/spec_auth_basic.rb' + for f in 'test/*.rb' + ruby -Ilib -e 'require '\''rubygems'\''; load "test/spec_auth_digest.rb" ' ./test/spec_auth_digest.rb:5: undefined method `describe' for main:Object (NoMethodError) from -e:1:in `load' from -e:1 + FAILED_TESTS=' test/spec_auth_basic.rb test/spec_auth_digest.rb' + for f in 'test/*.rb' + ruby -Ilib -e 'require '\''rubygems'\''; load "test/spec_body_proxy.rb" ' ./test/spec_body_proxy.rb:5: undefined method `describe' for main:Object (NoMethodError) from -e:1:in `load' from -e:1 + FAILED_TESTS=' test/spec_auth_basic.rb test/spec_auth_digest.rb test/spec_body_proxy.rb' + for f in 'test/*.rb' + ruby -Ilib -e 'require '\''rubygems'\''; load "test/spec_builder.rb" ' ./test/spec_builder.rb:21: undefined method `describe' for main:Object (NoMethodError) from -e:1:in `load' from -e:1 + FAILED_TESTS=' test/spec_auth_basic.rb test/spec_auth_digest.rb test/spec_body_proxy.rb test/spec_builder.rb' + for f in 'test/*.rb' + ruby -Ilib -e 'require '\''rubygems'\''; load "test/spec_cascade.rb" ' ./lib/rack/cascade.rb:7: uninitialized constant Rack::Cascade::CONTENT_TYPE (NameError) from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require' from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require' from ./test/spec_cascade.rb:1 from -e:1:in `load' from -e:1 ... Should this build submitted to the epel6 testing repository? This message is a reminder that EPEL 6 is nearing its end of life. Fedora will stop maintaining and issuing updates for EPEL 6 on 2020-11-30. It is our policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of 'el6'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later EPEL version. Thank you for reporting this issue and we are sorry that we were not able to fix it before EPEL 6 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. This message is a reminder that EPEL 6 is nearing its end of life. Fedora will stop maintaining and issuing updates for EPEL 6 on 2020-11-30. It is policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of 'el6'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later EPEL version. Thank you for reporting this issue and we are sorry that we were not able to fix it before EPEL 6 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version, you are encouraged to change the 'version' to a later version prior this bug is closed as described in the policy above. EPEL el6 changed to end-of-life (EOL) status on 2020-11-30. EPEL el6 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of EPEL please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |