GHOSTNET›MODULES›MOD-06 // WEB APPLICATION ATTACKS
CONCEPTLAB →
ADVANCED MODULE · CONCEPT PAGE · 10 CHAPTERS

WEB APPLICATION ATTACKS

OWASP Top 10 · Burp Suite mastery · SQLi · XSS · SSRF · XXE · JWT · OAuth · Deserialization · WAF bypass

10
CHAPTERS
~3.5hr
TOTAL READ
ADVANCED
DIFFICULTY
MOD-06
IDENTIFIER
BEGINNER~14 min READCHAPTER 1 OF 10

Web Application Testing Methodology

KEY POINTS · THE QUICK VERSION
  • OWASP Top 10 2021 is the canonical reference list for web app risk categories - not a complete vuln list
  • Burp Suite Pro is the industry-standard proxy; learn every tab before calling yourself a web tester
  • Establish scope and target mapping BEFORE active scanning to avoid missing attack surface
  • HTTP security headers (CSP, HSTS, CORS, X-Frame-Options) reveal the security maturity of the target
  • API testing (REST, GraphQL, gRPC) requires different tooling and mindset from traditional web testing
Scan these first, then read below for the depth and examples — or jump straight to the lab.

Web application testing is the largest subdomain of offensive security. Every modern organisation runs web apps, APIs, and microservices - all of which carry their own attack surface. This chapter covers the methodology, tooling, and conceptual framework you need before touching any target.

◈ PICTURE IT — MTAANI EDITION

A big Naivas branch keeps a ranked list of the ten commonest ways stock walks out the door — the unwatched exit, the faked receipt, the shelf left in a blind spot. OWASP's Top 10 is that same ranked list for websites: not every possible theft, but the ten that catch the most victims, so you check these first before anything exotic.

► OWASP Top 10 2021 - Full Breakdown

The OWASP Top 10 is a community-consensus document listing the most critical web application security risks. The 2021 edition reorganised categories significantly. It is a risk classification, not a vulnerability checklist - each category contains dozens of specific vulnerability classes.

RankCategoryWhat It CoversKey Examples
A01Broken Access ControlFailures in enforcing what authenticated users are allowed to doIDOR, privilege escalation, CORS misconfig, path traversal to protected files
A02Cryptographic FailuresSensitive data exposed due to weak or absent encryptionHTTP instead of HTTPS, MD5 passwords, weak TLS, hardcoded secrets in code
A03InjectionUntrusted data sent to an interpreter as a command or querySQL injection, command injection, LDAP injection, XSS, template injection
A04Insecure DesignArchitectural flaws - not just implementation bugsNo rate limiting on auth, missing business logic controls, trusting client-side checks
A05Security MisconfigurationDefault configs, unnecessary features, verbose error messagesDefault creds, exposed stack traces, open S3 buckets, debug endpoints in prod
A06Vulnerable ComponentsUsing libraries/frameworks with known CVEsLog4Shell via log4j, old jQuery, outdated OpenSSL, unpatched CMS plugins
A07Auth and Session FailuresBroken authentication and session managementWeak passwords, no MFA, predictable session tokens, session fixation
A08Software/Data Integrity FailuresCode and infrastructure not protected from integrity violationsInsecure deserialization, unsigned software updates, CI/CD pipeline injection
A09Security Logging FailuresInsufficient logging and monitoring enables attackers to persistNo audit logs, no alerting on brute force, logs not protected from tampering
A10SSRFServer-side request forgery - server makes requests on behalf of attackerAWS metadata access, internal port scanning, Redis/Elasticsearch exploitation

► Web App Testing Methodology

👁 WATCH THIS · you don't need to run it yet — just read along
// PHASE 1: PASSIVE RECON - NO ACTIVE PROBING YET
# Technology fingerprinting:
whatweb https://TARGET_URL              # identifies CMS, framework, server
wappalyzer (browser extension)          # same but in browser
curl -I https://TARGET_URL              # grab response headers

# DNS / subdomain enumeration:
subfinder -d target.com -o subs.txt
amass enum -passive -d target.com
# Look for: dev., staging., admin., api., beta., old., internal.

# Certificate transparency (no active probing needed):
curl "https://crt.sh/?q=%.target.com&output=json" | jq '.[].name_value'

# Search engine dorking (passive):
# site:target.com ext:php
# site:target.com inurl:admin
# site:target.com "error" OR "exception" OR "stack trace"

# Wayback Machine - find old endpoints:
# https://web.archive.org/web/*/target.com/*
# waybackurls target.com | tee wayback.txt
What you're seeing: This is a tester's opening move: quietly asking public sources what a site is built from and which other addresses belong to it, without yet poking the site itself. Every line here only reads information that is already out in the open.
↪ You'll run this recon against a safe practice target in the ↪ MOD-06 lab.
// PHASE 2: ACTIVE MAPPING - ENUMERATE ATTACK SURFACE
# Directory and file brute-force:
ffuf -w /usr/share/wordlists/dirb/common.txt -u https://TARGET_URL/FUZZ
gobuster dir -u https://TARGET_URL -w /usr/share/seclists/Discovery/Web-Content/raft-large-directories.txt

# Parameter discovery:
arjun -u https://TARGET_URL/endpoint -oT params.txt
# or: ffuf -w params_wordlist.txt -u "https://TARGET_URL/?FUZZ=1"

# API endpoint discovery:
kiterunner scan https://TARGET_URL -w routes-large.kite

# JS file mining for secrets and hidden endpoints:
# Download all .js files, grep for: api_key, token, password, endpoint, /api/
gau target.com | grep ".js$" | sort -u | tee js_files.txt

► Burp Suite Pro - Complete Workflow

// BURP SUITE CORE WORKFLOW
# 1. PROXY SETUP
# Burp: Proxy > Options > Proxy Listeners > 127.0.0.1:8080
# Browser: set proxy to 127.0.0.1:8080
# Install Burp CA cert: http://burpsuite > CA Certificate > import in browser

# 2. TARGET SCOPE
# Target > Scope > Add > Enter target domain
# Proxy > Options > "Intercept requests based on rules" > check "is in scope"
# This prevents capturing noise from ad networks/CDNs

# 3. SPIDERING / CRAWLING
# Target > Site map: right-click target > Scan (or Spider in older versions)
# Passively crawls via proxy traffic
# Engagement tools > Find references (searches JS for endpoints)

# 4. SCANNER (Pro only)
# Right-click any request > Scan
# Scanner > Dashboard: live issue feed
# Issue types: Active (probes) vs Passive (header analysis)

# 5. INTRUDER - automated fuzzing
# Capture request > Send to Intruder (Ctrl+I)
# Positions tab: highlight payload position > Add marker
# Payloads tab: choose list type (Simple list, Numbers, Cluster bomb, Pitchfork)
# Cluster bomb: all combos of multiple wordlists (e.g. user + password brute force)
# Pitchfork: parallel - position 1 from list A, position 2 from list B (credential stuffing)

# 6. REPEATER - manual request modification
# Send to Repeater (Ctrl+R)
# Modify headers, body, cookies, method
# Compare responses with Comparer

# 7. DECODER
# Decode/encode: URL, Base64, HTML, Hex, Gzip, ZLIB
# Smart decode: auto-detects encoding layers

# 8. SEQUENCER - token entropy analysis
# Load a session token generation request
# Captures tokens and analyses randomness (FIPS 140-2 tests)
# Low entropy = predictable session tokens = account takeover

# 9. COMPARER
# Word/byte diff between two requests or responses
# Detect subtle differences in blind injection responses
// KEY BURP EXTENSIONS
# Install via Extensions > BApp Store

# ActiveScan++ - augments scanner with extra checks
# Turbo Intruder - high-speed fuzzing (Python scripts, race condition testing)
# Autorize - automatically tests all requests as a lower-privileged user
#   → Add low-priv cookie → Autorize replays every request with low-priv creds
#   → Red = access granted (should be forbidden) = broken access control
# Param Miner - discovers unlinked parameters via header/body injection
# J2EEScan - Java EE specific checks (Struts, JBoss, WebLogic, JMX)
# Collaborator Everywhere - injects Burp Collaborator payloads into all headers
#   → Detects blind SSRF, blind XXE, DNS rebinding vulnerabilities
# HTTP Request Smuggler - desync attack detection and exploitation
# JWT Editor - full JWT attack suite (none alg, key confusion, crack)
# InQL - GraphQL introspection, query generation, scanning

► HTTP Security Headers Analysis

HeaderPurposeMissing = Vulnerable ToSecure Value
Content-Security-PolicyRestricts resource loading originsXSS via inline scripts or external CDNsdefault-src 'self'; script-src 'self'
Strict-Transport-SecurityForces HTTPS for a durationSSL stripping, downgrade attacksmax-age=31536000; includeSubDomains
X-Frame-OptionsPrevents iframe embeddingClickjacking attacksDENY or SAMEORIGIN
X-Content-Type-OptionsPrevents MIME sniffingContent type confusion attacksnosniff
Access-Control-Allow-OriginCORS policyCross-origin data theft if wildcardSpecific origin, not *
Referrer-PolicyControls Referer header valueInformation leakage via Refererstrict-origin-when-cross-origin
Permissions-PolicyRestricts browser featuresGeolocation/camera/mic abusegeolocation=(), camera=()

► API Testing Overview

// DIFFERENCES IN API TESTING APPROACH
# REST API
# - Endpoints: /api/v1/users, /api/v1/orders/ORD_ID
# - Auth: Bearer token in Authorization header, API key in header or param
# - Test: verb tampering (GET->POST->DELETE), versioning (v1->v2->v0)
# - Tool: Burp Suite, Postman, ffuf for endpoint discovery

# GraphQL
# - Single endpoint: /graphql or /api/graphql
# - All requests are POST with JSON body containing "query" field
# - Test: introspection, batching, depth attacks, field suggestions
# - Tool: InQL (Burp), GraphQL Voyager, Altair

# SOAP / XML Web Services
# - WSDL file describes all operations: TARGET_URL?wsdl
# - All messages are XML - test for XXE inside SOAP body
# - Tool: SOAPUI, Burp (intercept and modify XML)

# gRPC
# - Uses Protocol Buffers (binary) not JSON - need to decode .proto files
# - Find .proto files in APKs, JS bundles, GitHub repos
# - Tools: grpcurl (curl for gRPC), grpcui (web UI), BloomRPC
grpcurl -plaintext TARGET_HOST:PORT list         # list services
grpcurl -plaintext TARGET_HOST:PORT describe svc  # describe methods
grpcurl -d '{"user_id": "1"}' TARGET_HOST:PORT service.Method
PRO TIP
OWASP ZAP is the free alternative to Burp Pro. Use ZAP for CI/CD pipeline integration (DAST in automation), and Burp for manual testing. ZAP has better scripting support for custom scan rules; Burp has superior manual request manipulation.
RECAP · CHECK YOURSELF
  • OWASP Top 10 2021 is the canonical reference list for web app risk categories - not a complete vuln list
  • Burp Suite Pro is the industry-standard proxy; learn every tab before calling yourself a web tester
  • Establish scope and target mapping BEFORE active scanning to avoid missing attack surface
  • HTTP security headers (CSP, HSTS, CORS, X-Frame-Options) reveal the security maturity of the target
  • API testing (REST, GraphQL, gRPC) requires different tooling and mindset from traditional web testing
Read to the end to count this chapter
▸ READY TO PRACTISE
You've now covered enough for Lab steps 1–2 of 21. Try them in the lab while it's fresh.
OPEN LAB ▸
⚡ TEST YOURSELF
End-of-chapter quiz
A dozen questions — recall and practical. Graded, earns up to 20 XP.
PRACTISE IN THE LAB ▸
READY TO PRACTICE?
MOD-06 Interactive Lab
21 steps · 445 XP · Real commands · Flag captures
LAUNCH LAB →
← MOD-05: ACTIVE DIRECTORYMOD-07: MALWARE →