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>] [day] [month] [year] [list]
From: PerrymonJ at (Perrymon, Josh L.)
Subject: SANS GDIscan

I get the same thing. I see a lot of indifferences with the locations of the
.DLL --

Also patched systems from M$ update and SMS patch pushes and still get
vulnerable .DLLs using the Scanner from SANS?

Does the M$ patch really fix this issue?

I'm going to take a patched box and run some exploits on it in the lab to
see the results.


-----Original Message-----
From: bashis [] 
Sent: Sunday, September 26, 2004 10:34 AM
Subject: [Full-Disclosure] SANS GDIscan


I tested [1] 'gdiscan' from SANS, and this tool reports vulnerable DLL's
after installing all availible patches from M$..

WinXP Pro SP1
   Version: 5.1.3097.0 <-- Vulnerable version 

Win2k Server SP4
C:\Program Files\Common Files\Microsoft Shared\Ink\gdiplus.dll
   Version: 5.1.3097.0 <-- Vulnerable version 


Have a nice day

Full-Disclosure - We believe in it.

Powered by blists - more mailing lists