ESF Exploit Next Generation® SQL Fingerprint™

SQL Server fingerprinting can be a time consuming process. It involves a lot many trial and error methods to fingerprint the exact SQL Server  version. Intentionally inserting an invalid input to obtain a typical error message or using certain alphabets that are unique for a certain server are two of the ways to possibly fingerprint a server. But, when it comes to the Microsoft SQL Server fingerprinting, Exploit Next Generation® SQL Fingerprint™ (f.k.a. Microsoft SQL Server Fingerprint Tool) tool is the best!

The Exploit Next Generation® SQL Fingerprint™ (ESF) is a powerful tool which performs version fingerprinting for:

   1. Microsoft SQL Server 2000;
   2. Microsoft SQL Server 2005; and
   3. Microsoft SQL Server 2008.

The Exploit Next Generation® SQL Fingerprint™ uses well-known techniques based on several public tools that are capable to identify the Microsoft SQL Server version (such as: SQLping and SQLver), but, instead of showing only the "raw version" (i.e., Microsoft SQL Version 10.00.2746), the Exploit Next Generation® SQL Fingerprint™ shows the mapped Microsoft SQL Server version (i.e., Microsoft SQL 2008 SP1 (CU5)).

The strengths of Exploit Next Generation® SQL Fingerprint™ are:
   1. It uses both TCP and UDP protocols to determine the Microsoft SQL Server version, making it much more reliable than any other public or commercial tool.
   2. It is capable to identify multiple Microsoft SQL Server instances and their TCP communication ports.
   3. It does not require any authentication method to identify the Microsoft SQL Server version.
   4. It uses probabilistic algorithm to identify the Microsoft SQL Server version, combining both TCP and UDP fingerprint.

SQL Server fingerprinting is necessary before performing any kind of penetration testing on database server and if you find its Microsoft SQL Server then this tool will surely help identifying granular level findings to further exploit database.

To download ESF:
http://code.google.com/p/esf/downloads/list

Wireshark Cookie Dump: