[9563] in bugtraq
Re: NT too? Re: Another Windows98 Bug...
daemon@ATHENA.MIT.EDU (Bayerkohler, Marcus)
Sat Feb 13 18:00:46 1999
Date: Fri, 12 Feb 1999 16:56:31 -0600
Reply-To: "Bayerkohler, Marcus" <Marcus_Bayerkohler@EXCHANGE.BMC.COM>
From: "Bayerkohler, Marcus" <Marcus_Bayerkohler@EXCHANGE.BMC.COM>
X-To: Clifford Hammerschmidt <chammers@PIM.BC.CA>
To: BUGTRAQ@NETSPACE.ORG
i had mixed results. i created the file on a linux box.
ie would not let you save it on an nt box. (gives error)
netscape would let you save the file.
on different nt4sp3 machines i had this reaction:
2 machines: no problem, right click and get menu
1 machine: right click, screen blanks to its wallpaper then returns to
desktop and brings up a FindFast window.
1 machine: right click, screen blanks to its wallpaper then returns to
destop and brings up an error about the c: drive not found, then a FindFast
window.
marc
> -----Original Message-----
> From: Clifford Hammerschmidt [mailto:chammers@PIM.BC.CA]
> Sent: Thursday, February 11, 1999 1:25 PM
> To: BUGTRAQ@netspace.org
> Subject: NT too? Re: Another Windows98 Bug...
>
>
> The following perl script will create a 250 character file
> that will crash
> WinNT (service pack 3) explorer when right-clicked on:
> --------------------
> $fn = 'A' x 250;
> open (FH,">$fn") or die ":$!\n";
> print FH "it worked?";
> close FH;
> --------------------
>
> You may have to create the file inside a subdirectory. I think what is
> happening here is the path+filename exceeds MAX_PATH.
>
> To delete the file drop to a command window and delete it using it's
> shortname (dir /X will display shortnames).
>
> At 05:49 PM 2/9/98 -0800, you wrote:
> >>>>
> I'm not sure about the details of this problem, but when
> testing another
> buffer overflow, I created a long filename called "testfile.txt
>
>
> "
> (note the chr(160)'s at the end) It is 235 characters in
> length. After
> creating it on my desktop, I right clicked on it; explorer
> crashed saying
> it caused an illegal operation. the only way I found to
> close this was by
> using command.com I sent this to a friend and he got the same error.
>
> -Scott Campbell
(<mailto:smc@visuallink.com>smc@visuallink.com)
<<<<
