Fingerprint Web Application Framework
OWASP Web Security Testing Guide 4.2 > 1. Information Gathering > 1.8. Fingerprint Web Application Framework
ID | Link to Hackinglife | Link to OWASP | Objectives |
---|---|---|---|
1.8 | WSTG-INFO-08 | Fingerprint Web Application Framework | - Fingerprint the components being used by the web applications. - Find the type of web application framework/CMS from HTTP headers, Cookies, Source code, Specific files and folders, Error message. |
HTTP headers
- Note the response header
X-Powered-By
, orX-Generator
as well. - Identify framework specific cookies. For instance, the cookie
CAKEPHP
for php.
HTML source code
- Framework is often include in the
META
tag. - Revise header and footer sections carefully: general markers and specific markers.
- See typical file and folders structure. An example would be wp-includes folder for a wordpress installation, or a CHANGELOG file for a Drupal one.
- Check out file extensions, as sometimes they reveals the underlying framework.
- Revise error messages. They commonly reveals framework.
See WSTG-INFO-07 for a reference to HTTRack for mirrowing the code and EyeWitness. These utilities replicated the source code of the target domain.
Tools
1. HTTP headers:
X-Powered-By and cookies:
- .NET: ASPSESSIONID<RANDOM>=<COOKIE_VALUE>
- PHP: PHPSESSID=<COOKIE_VALUE>
- JAVA: JSESSION=<COOKIE_VALUE>
2. whatweb.
3. Wappalyzer: https://www.wappalyzer.com.
4. wafw00f:
5. Aquatone
6. Addons for browsers:
- BuiltWith: BuiltWith® covers 93,551+ internet technologies which include analytics, advertising, hosting, CMS and many more.
7. Curl:
8. nmap: