Skip to main content
The web service is the most common and extensive service and a wide variety of vulnerability types exist. Default Ports: 80 (HTTP), 443 (HTTPS)

Methodology Overview

1

Identify Technologies

Find the technologies being used to look for known vulnerabilities and useful tricks.
2

Check for WAF

3

Launch General Scanners

4

Initial Checks

Check default informational pages:
  • /robots.txt
  • /sitemap.xml
  • /crossdomain.xml
  • /.well-known/
  • Check comments in main and secondary pages
Run SSL/TLS scan if HTTPS:
5

Spider the Application

Find all possible files, folders, and parameters:
6

Directory Brute-Forcing

7

Backup Checking

Check for backup files appending common extensions: file.ext~, #file.ext#, ~file.ext, file.ext.bak, file.ext.tmp, file.ext.old
8

Parameter Discovery

9

Vulnerability Checking

Use the web vulnerabilities methodology checklist for all discovered endpoints.

Technology-Specific Tricks

If source code is available on GitHub:
  • Check Change-log/Readme for version info
  • Look for credentials in code, configs, commit history
  • Search for hash algorithms, encryption keys
  • Check Issues for unresolved vulnerabilities
  • .git directory exposed → extract source code
  • .env file → API keys, DB passwords
  • JS files → use RetireJS to check for known vulnerabilities
  • API endpoints → test for API-specific vulnerabilities
  • 403 Forbidden → try bypass techniques
  • 502 Proxy Error → potential misconfigured proxy/SSRF
  • NTLM Authentication → info disclosure via NTLM challenge

NTLM Authentication Info Disclosure

Automated Command Reference

SSL/TLS Vulnerability Reference

  • No HTTPS enforcement → MitM possible
  • Sensitive data in HTTP → high severity
  • Check for BEAST, POODLE, HEARTBLEED, ROBOT, DROWN via testssl.sh