|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |
Date: Tue, 29 Apr 2003 13:00:55 -0700 Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v552) To: "ERRor" <error@pochtamt.ru> From: Cove Schneider <cove@wildpackets.com> In-Reply-To: <000501c30e7c$71165b50$9801a8c0@nobody> Message-Id: <49B0A2C1-7A7D-11D7-9140-000393941C60@wildpackets.com> Content-Transfer-Encoding: 7bit Spoke too soon. Safari eventually become responsive after a while. On Tuesday, April 29, 2003, at 11:23 AM, ERRor wrote: > Hello, Bugtraq. > > Malicious htm file can freeze IE with 100% CPU usage: > Construct the file freeze.htm: > c:\>perl -e "print qq'\xFF\xFE'; print qq'\r\n' x 30000" > freeze.htm > > After opening freeze.htm IE will hang with 100% CPU usage until > IEXPLORE.EXE > process is not killed. Two bytes (0xff 0xfe) at the beginning of the > file > mean that > the encoding is unicode. So the internal unicode representation of the > CR LF > sequence > will look like 0D0A0D0A but not 000D000A (if the file was a plain > ASCII). > Tested on IE 6.0 with all fixes, i think other versions also > vulnerable. > > > Best Regards, ERRor, dHtm. > P.S. greets to .einstein. and dHtm >
|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |