performing-http-parameter-pollution-attack

name	performing-http-parameter-pollution-attack
description	Execute HTTP Parameter Pollution attacks to bypass input validation, WAF rules, and security controls by injecting duplicate parameters that are processed differently by front-end and back-end systems. Use when working with performing http parameter pollution attack.
domain	cybersecurity
tags	["http-parameter-pollution","hpp","waf-bypass","input-validation","web-security","parameter-injection","server-parsing"]
subdomain	web-application-security
version	1.0
author	oyi77
license	Apache-2.0
nist_csf	["PR.PS-01","ID.RA-01","PR.DS-10","DE.CM-01"]

Performing Http Parameter Pollution Attack

Overview

Cybersecurity skill for performing http parameter pollution attack. Follows industry best practices and security standards.

When to Use

Trigger phrases:

• "performing http parameter pollution attack"

• "Execute HTTP Parameter Pollution attacks to bypass input validation, WAF rules, "

• When testing web applications for input validation bypass vulnerabilities

• During WAF evasion testing to split attack payloads across duplicate parameters

• When assessing how different technology stacks handle duplicate HTTP parameters

• During API security testing to identify parameter precedence issues

• When testing OAuth or payment processing flows for parameter manipulation

When NOT to Use

• When you lack proper authorization for testing
• For production systems without change management
• When the task requires legal or compliance expertise beyond technical scope

Prerequisites

• Burp Suite Professional with Intruder and Repeater modules
• Understanding of HTTP protocol and query string parsing
• Knowledge of server-side parameter handling differences (first, last, array, concatenated)
• cURL or httpie for manual parameter crafting
• Target application technology stack identification (Apache, IIS, Tomcat, Node.js, etc.)

Legal Notice: This skill is for authorized security testing and educational purposes only. Unauthorized use against systems you do not own or have written permission to test is illegal and may violate computer fraud laws.

Workflow

# Example: IOC detection
import re

IOC_PATTERNS = {
    "ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",
    "domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",
    "hash_md5": r"\b[a-f0-9]{32}\b",
    "hash_sha256": r"\b[a-f0-9]{64}\b",
}

def extract_iocs(text: ) -> :
     {k: re.findall(v, text)  k, v  IOC_PATTERNS.items()}