WAFP v0.01 - Web Application Finger Printer

WAFP is a Web Application Finger Printer written in ruby using a SQLite3 DB.

Hot it works?

WAFP fetches the files given by the Finger Prints from a webserver and checks if the checksums of those files are matching to the given checksums from the Finger Prints. This way it is able to detect the detailed version and even the build number of a Web Application.

In detail?

A Web Application Finger Print consits of a set of relative file locations in conjunction with their md5sums. It is made based on a production or example installation of a Web Application or just out of an extracted Web Application install files tarball. For this task, generate_wafp_fingerprint.sh is to be used.

Requirements

  • ruby >= 1.8
  • sqlite3 >= 3
  • sqlite3-ruby >= 1.2.4

Compile and Install

Not needed.

Usage

The script will be executed via:

./generate_wafp_fingerprint.sh [OPTIONS]

The following list contains the available Options:

  • APPLICATION_PATH: should be the path to the Web Application files - like the content of the htdocs folder of a wordpress installation. The folder containing the Web Application files must be named like this: APPLICATIONNAME-MAJORVERSION.VERSION.SUB.ASO-RC-ALPHA-BETA
  • FINGERPRINT_FILE: is the path to a file containing exported Finger Prints.
  • EXPORT: this means the generated Finger Print data will not be stored within the DB but printed to stdout in a format which can be imported with IMPORT.
  • IMPORT: can be used to import some EXPORTED fingerprints.

More information: here

MD5:

-----
wafp-0.01-26c3.tar.lzma | 7905bd6327492872fb3044badf90b84c
wafp-0.01-26c3.tar.bz2  | 1d99ead23df26ab5c04438f7e5d48007
wafp-0.01-26c3.tar.gz   | 4a34f7c83a54ab7900ad915db847e74e
-----

Post scriptum


Comments

Related Articles

Configurations checks
Enumeration
Information Gathering
WAFP