AUTHORIZED USE ONLY: Use this skill only for authorized security assessments, defensive validation, or controlled educational environments.

Burp Suite Web Application Testing

Purpose

Execute comprehensive web application security testing using Burp Suite's integrated toolset, including HTTP traffic interception and modification, request analysis and replay, automated vulnerability scanning, and manual testing workflows. This skill enables systematic discovery and exploitation of web application vulnerabilities through proxy-based testing methodology.

Inputs / Prerequisites

Required Tools

• Burp Suite Community or Professional Edition installed
• Burp's embedded browser or configured external browser
• Target web application URL
• Valid credentials for authenticated testing (if applicable)

Environment Setup

• Burp Suite launched with temporary or named project
• Proxy listener active on 127.0.0.1:8080 (default)
• Browser configured to use Burp proxy (or use Burp's browser)
• CA certificate installed for HTTPS interception

Editions Comparison

Outputs / Deliverables

Primary Outputs

• Intercepted and modified HTTP requests/responses
• Vulnerability scan reports with remediation advice
• HTTP history and site map documentation
• Proof-of-concept exploits for identified vulnerabilities

Core Workflow

Phase 1: Intercepting HTTP Traffic

#### Launch Burp's Browser Navigate to integrated browser for seamless proxy integration:

1. Open Burp Suite and create/open project
2. Go to Proxy > Intercept tab
3. Click Open Browser to launch preconfigured browser
4. Position windows to view both Burp and browser simultaneously

#### Configure Interception Control which requests are captured:

Proxy > Intercept > Intercept is on/off toggle

When ON: Requests pause for review/modification
When OFF: Requests pass through, logged to history

#### Intercept and Forward Requests Process intercepted traffic:

1. Set intercept toggle to Intercept on
2. Navigate to target URL in browser
3. Observe request held in Proxy > Intercept tab
4. Review request contents (headers, parameters, body)
5. Click Forward to send request to server
6. Continue forwarding subsequent requests until page loads

#### View HTTP History Access complete traffic log:

1. Go to Proxy > HTTP history tab
2. Click any entry to view full request/response
3. Sort by clicking column headers (# for chronological order)
4. Use filters to focus on relevant traffic

Phase 2: Modifying Requests

#### Intercept and Modify Change request parameters before forwarding:

1. Enable interception: Intercept on
2. Trigger target request in browser
3. Locate parameter to modify in intercepted request
4. Edit value directly in request editor
5. Click Forward to send modified request

#### Common Modification Targets

#### Example: Price Manipulation

POST /cart HTTP/1.1
Host: target.com
Content-Type: application/x-www-form-urlencoded

productId=1&quantity=1&price=100

# Modify to:
productId=1&quantity=1&price=1

Result: Item added to cart at modified price.

Phase 3: Setting Target Scope

#### Define Scope Focus testing on specific target:

1. Go to Target > Site map
2. Right-click target host in left panel
3. Select Add to scope
4. When prompted, click Yes to exclude out-of-scope traffic

#### Filter by Scope Remove noise from HTTP history:

1. Click display filter above HTTP history
2. Select Show only in-scope items
3. History now shows only target site traffic

#### Scope Benefits

• Reduces clutter from third-party requests
• Prevents accidental testing of out-of-scope sites
• Improves scanning efficiency
• Creates cleaner reports

Phase 4: Using Burp Repeater

#### Send Request to Repeater Prepare request for manual testing:

1. Identify interesting request in HTTP history
2. Right-click request and select Send to Repeater
3. Go to Repeater tab to access request

#### Modify and Resend Test different inputs efficiently:

1. View request in Repeater tab
2. Modify parameter values
3. Click Send to submit request
4. Review response in right panel
5. Use navigation arrows to review request history

#### Repeater Testing Workflow

Original Request:
GET /product?productId=1 HTTP/1.1

Test 1: productId=2    → Valid product response
Test 2: productId=999  → Not Found response  
Test 3: productId='    → Error/exception response
Test 4: productId=1 OR 1=1 → SQL injection test