Thanks to Tom Liston for writing this program
gdiscan.exe was written for Windows 2000 and higher. It scans the drive containing the Windows %system% directory and Looks for vulnerable versions of gdiplus.dll, sxs.dll, wsxs.dll, mso.dll and vgx.dll.
The scan starts upon execution. It will signal completion of scan in text box with "Done."
Vulnerable versions of the .dll files are listed in RED.
The path where a vulnerable .dll file is found is important. Remember hat dlls are loaded in the following order (note: this is a VAST simplification):
- The directory from which the application loaded.
- The (application's) current directory.
- Windows 95/98: The Windows system directory (default: C:\Windows\system)
- Windows NT+: The 32-bit Windows system directory (default: C:\WinNT\System32)
- Windows NT+: The 16-bit Windows system directory (default: C:\WinNT\System)
- The Windows directory (default: C:\WinNT or C:\Windows)
- The directories that are listed in the PATH environment variable
Frequently Asked Questions (FAQ)
Q: Are there any files I should ignore?
A: Ignore files in directories like Windows\$NtUniinstallKBxxxxx\. These are old versions left behind for uninstal purposes.
Q: What command line options are there?
A: The only parameter for the command line option is the log filename (usage: gdiclscan.exe logfile). It will exit with a return code of 1 if it can not open the log file. The command line version will not overwrite the log file.
Q: Can I use options with the GUI?
A: There are no options for the GUI version. Please use the command line version.
Note: we do keep this tool here for historic purposes. It is WAY out of date and was used for one specific issues many years ago.
GUI version (Ver. 2.1)
(updated. Version 2 will allow you to scan arbitrary drives)
. People keep asking for a stronger hash. So here is a SHA512 hash of the file: 245ba1666c7dd3facac649e39dd71b0fdfe3ba9ca467eb53bfd2c16c040dda1eac039970fe080d8259e96eea0e78f9c8f971fa2f31382e2f4201266cf2c36190 . But note, that it is as useless as the MD5 hash above. Note how it comes from the same server as the .exe ? What do you think someone can do if they can modify the file? They will modify this page too... There is a PGP signature below as well, which should be used instead if you actually care about the file's integrity.
Command Line Version (Ver. 2.1)
(Ver. 2.1 now includes scanning on arbitrary drives)
License: You may freely copy and use this binary. Please do not mirror the file, as updates may be made available at any time without notice. If you link to this tool, link to http://isc.sans.edu/gdiscan.php.