lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
From: rlanguy at (Lan Guy)
Subject: Microsoft's Explorer and Internet Explorer long share name buffer overflow.

Even people like Christopher Hertel
don't know the maximum limit of a share name.
I always thought that the protocol could not have more than 127 charaters in 
a single share name length.

In any case Explorer should not crash.
 Lan Guy

----- Original Message ----- 
From: "KF (lists)" <>
To: <>
Cc: <>
Sent: Thursday, April 29, 2004 2:55 AM
Subject: Re: [Full-Disclosure] Microsoft's Explorer and Internet Explorer 
long share name buffer overflow.

>I would say they lied myself... I have all patches from Windows update 
>installed including all the optional ones... still crashes for me and still 
>tears up the EIP and EBP. My IE advertises itself as: 6.0.2800.1106 SP1; 
>Q837009;Q8832894:Q831167 , The OS is Win2k Server 5.00.2195 SP4.
> Thus far I have been unable to locate a good unicode return address... but 
> thats not to say there is not one there. =] . For those of you wondering 
> smb.conf DOES allow for characters like \x90 and other things of that 
> nature.
> enjoy.
> -KF
> Paul Szabo wrote:
>>Anyway, lies when it says this 
>>fixed in W2kSP4; or maybe that KB article refers to a different problem: 
>>say the error should be "Access Violation", I got "Program Error".
>>Paul Szabo - 
>>School of Mathematics and Statistics  University of Sydney   2006 
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter:

Powered by blists - more mailing lists