|author||Eric Wong <firstname.lastname@example.org>||2010-04-19 13:47:29 -0700|
|committer||Eric Wong <email@example.com>||2010-04-19 13:47:29 -0700|
This release fixes a denial-of-service vector for deployments exposed directly to untrusted clients. The HTTP parser in Unicorn <= 0.97.0 would trip an assertion (killing the associated worker process) on invalid Content-Length headers instead of raising an exception. Since Rainbows! and Zbatery supports multiple clients per worker process, all clients connected to the worker process that hit the assertion would be aborted. Deployments behind nginx are _not_ affected by this bug, as nginx will reject clients that send invalid Content-Length headers. The status of deployments behind other HTTP-aware proxies is unknown. Deployments behind a non-HTTP-aware proxy (or no proxy at all) are certainly affected by this DoS. Users are strongly encouraged to upgrade as soon as possible, there are no other changes besides this bug fix from Rainbows! 0.91.0 nor Unicorn 0.97.0 This bug affects all previously released versions of Rainbows! and Zbatery.
3 files changed, 5 insertions, 5 deletions
diff --git a/GIT-VERSION-GEN b/GIT-VERSION-GEN
index 366063e..95d54f9 100755
@@ -1,7 +1,7 @@
diff --git a/lib/rainbows/const.rb b/lib/rainbows/const.rb
index 4250866..99fb257 100644
@@ -3,7 +3,7 @@
- RAINBOWS_VERSION = '0.91.0'
+ RAINBOWS_VERSION = '0.91.1'
diff --git a/rainbows.gemspec b/rainbows.gemspec
index 0fda618..579088f 100644
@@ -41,9 +41,9 @@ Gem::Specification.new do |s|
s.test_files = test_files
# we need Unicorn for the HTTP parser and process management
- # The HTTP parser in Unicorn < 0.96.1 did not use the Ruby
- # API correctly and resulted in a memory leak
- s.add_dependency(%q<unicorn>, ["~> 0.97.0"])
+ # The HTTP parser in Unicorn <= 0.97.0 was vulnerable to a remote DoS
+ # when exposed directly to untrusted clients.
+ s.add_dependency(%q<unicorn>, ["~> 0.97.1"])
# Unicorn already depends on Rack