It was discovered that WEBrick incorrectly handled having both a Content- Length header and a Transfer-Encoding header. A remote attacker could possibly use this issue to perform a HTTP request smuggling attack.
{ "availability": "No subscription required", "binaries": [ { "binary_version": "1.8.1-1ubuntu0.1", "binary_name": "ruby-webrick" } ] }