Bug 58066 – VNC can be frozen via HTTP

Bug 58066 - VNC can be frozen via HTTP

Summary:	VNC can be frozen via HTTP

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	vnc (Show other bugs)
Sub Component:
Version:	7.0
Hardware:	i686 Linux

Priority	medium Severity high
Target Milestone:	---
Target Release:	---
Assigned To:	Tim Waugh
QA Contact:	David Lawrence
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2002-01-07 12:49 EST by Tal Kelrich
Modified:	2007-04-18 12:38 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2002-02-08 05:41:10 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Tal Kelrich 2002-01-07 12:49:13 EST

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.5) Gecko/20011014

Description of problem:
vnc freezes when receiving HTTP requests, until all headers are sent (\n\n).

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


How reproducible:
Always

Steps to Reproduce:
$ nc box.victim.com 5801
GET / HTTP/1.1\n


Actual Results:  [vnc is now frozen until a second \n is entered, ending the
header section, or until http disconnect]

Expected Results:  nothing

Additional info:

vnc, RPM 3.3.3r1

Comment 1 Tim Waugh 2002-01-10 10:47:51 EST

There is another DoS that can be used to break out of this one. :-)
I'll talk to the maintainers.

Comment 2 Tim Waugh 2002-03-12 04:39:15 EST

Fixed in 3.3.3r2-18.3.

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