Vulnerability Development mailing list archives
Re: IE 5.x (5.50.4522.1800 SP1) Crash at gopher://:
From: "Marius Huse Jacobsen" <mahuja () c2i net>
Date: Sun, 20 May 2001 23:25:36 +0200
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 For reference, I'm using IE 5.50.4134.0100 From: "Fernando Merino Levadinha" <chuck () bn com br>
Hi list, it's seem to be a new bug, i crashed my IE 5.x (5.50.4522.1800 SP1) with this URL: gopher://:
Puts IE into a loop, that seems to spawn new threads all of the time. The longer it stays, the slower the computer gets, until IE (or just that window, not sure) is shut down. No real crashes though.
it's like an older BUG in IE 4.x (ftp://:)
ftp://: does nothing for me. (cannot find, make sure the address is correct) From: "Uidam, T (Tim)" <Tim.Uidam () SYD RABOBANK COM>
Didn't crash on mine, just like the FTP one doesn't crash on mine... As i said before, i _suspect_ that this is because i do NOT have the IE Browsing enhancements installed... you know the one that displays FTP sites like explorer...
I have 'em. ftp://*//#./ Gives me the gopher effect. From: "Kayne Ian (Softlab)" <Ian.Kayne () softlab co uk>
I tried test://:, it did nothing. Typing me://: auto-corrected the url to mk://:, if anyone knows what that is? So, just for a laugh I typed hello://: which auto-corrected to shell://:
It doesn't know those protocols on my comp. Anyway, I think I have some idea of why the "shell:" acts like it does. It spawns a window for each shell it gets an address to, with ';' as a separator? -----BEGIN PGP SIGNATURE----- Version: PGP 7.0.1 iQA/AwUBOwg17ailjHbgv3neEQK8YQCdHNvrkDjm56Y5jzCUCdZPySeHkcQAn00u 4soqvGEnA2kAJOD/3KwkR0hy =KSkk -----END PGP SIGNATURE-----
Current thread:
- IE 5.x (5.50.4522.1800 SP1) Crash at gopher://: Fernando Merino Levadinha (May 15)
- RE: IE 5.x (5.50.4522.1800 SP1) Crash at gopher://: Russ Spooner (May 16)
- Re: IE 5.x (5.50.4522.1800 SP1) Crash at gopher://: Jon Zobrist (May 21)
- Re: IE 5.x (5.50.4522.1800 SP1) Crash at gopher://: Kuk-hyun Lee (May 17)
- Re: IE 5.x (5.50.4522.1800 SP1) Crash at gopher://: Marius Huse Jacobsen (May 21)
- Re: IE 5.x (5.50.4522.1800 SP1) Crash at gopher://: Bruno Mosconi (May 21)
- <Possible follow-ups>
- RE: IE 5.x (5.50.4522.1800 SP1) Crash at gopher://: Uidam, T (Tim) (May 16)
- Re: IE 5.x (5.50.4522.1800 SP1) Crash at gopher://: Philip Stoev (May 17)
- RE: IE 5.x (5.50.4522.1800 SP1) Crash at gopher://: Jeremy Rodriguez (May 21)
- Re: IE 5.x (5.50.4522.1800 SP1) Crash at gopher://: Philip Stoev (May 17)
- RE: IE 5.x (5.50.4522.1800 SP1) Crash at gopher://: Kayne Ian (Softlab) (May 16)
- Re: IE 5.x (5.50.4522.1800 SP1) Crash at gopher://: Don Tansey (May 17)
- RE: IE 5.x (5.50.4522.1800 SP1) Crash at gopher://: Bo Stark (May 17)
- Re: IE 5.x (5.50.4522.1800 SP1) Crash at gopher://: Sven van ´t Veer (May 21)
- Re: IE 5.x (5.50.4522.1800 SP1) Crash at gopher://: Devdas Bhagat (May 21)
- RE: IE 5.x (5.50.4522.1800 SP1) Crash at gopher://: David Schwartz (May 21)
- Re: IE 5.x (5.50.4522.1800 SP1) Crash at gopher://: Sven van ´t Veer (May 21)
(Thread continues...)
- RE: IE 5.x (5.50.4522.1800 SP1) Crash at gopher://: Russ Spooner (May 16)