Bug 218289 - CVE-2006-6303 ruby's cgi.rb vulnerable infinite loop DoS
Summary: CVE-2006-6303 ruby's cgi.rb vulnerable infinite loop DoS
Alias: None
Product: Fedora
Classification: Fedora
Component: ruby   
(Show other bugs)
Version: 6
Hardware: All Linux
Target Milestone: ---
Assignee: Akira TAGOH
QA Contact: Bill Huang
URL: http://www.ruby-lang.org/en/news/2006...
Whiteboard: impact=low,reported=20061204,public=2...
Keywords: Security
Depends On:
TreeView+ depends on / blocked
Reported: 2006-12-04 14:18 UTC by Lubomir Kundrak
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-12-12 03:05:55 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Lubomir Kundrak 2006-12-04 14:18:59 UTC
+++ This bug was initially created as a clone of Bug #218287 +++

Description of problem:

JVN#84798830 described a problem in cgi.rb, which results in infinite loop after
certain HTTP request. While the original advisory is in Japan, you might want to
translate it with Babelfish. Anyways, it doesn't contain any useful information.
The upstream corrected the problem immediately in CVS and even released a new
package with patchlevel of 2.

Version-Release number of selected component (if applicable):

All supported versions (RHEL 2.1 to 5, and both FC 5 and FC 6) seem to contain
the vulnerable code.

How reproducible:

No reproducer.

Additional info:

The translated JVN avdisory:

-- Additional comment from lkundrak@redhat.com on 2006-12-04 09:09 EST --
Created an attachment (id=142732)
Upstream patch for ruby cgi.rb DoS

Comment 1 Akira TAGOH 2006-12-11 07:47:02 UTC
fixed in and

Comment 2 Fedora Update System 2006-12-11 16:14:06 UTC
ruby- has been pushed for fc6, which should resolve this issue.  If these problems are still present in this version, then please make note of it in this bug report.

Note You need to log in before you can comment on or make changes to this bug.