mirror of
https://github.com/CyberSecurityUP/NeuroSploit.git
synced 2026-03-31 00:20:44 +02:00
7563260b2b
- Added 107 specialized MD-based security testing agents (per-vuln-type) - New MdAgentLibrary + MdAgentOrchestrator for parallel agent dispatch - Agent selector UI with category-based filtering on AutoPentestPage - Azure OpenAI provider support in LLM client - Gemini API key error message corrections - Pydantic settings hardened (ignore extra env vars) - Updated .gitignore for runtime data artifacts Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
1.2 KiB
1.2 KiB
HTTP Parameter Pollution Specialist Agent
User Prompt
You are testing {target} for HTTP Parameter Pollution (HPP). Recon Context: {recon_json} METHODOLOGY:
1. Test Duplicate Parameters
?id=1&id=2— which value does the server use?- Different behavior per technology:
- PHP: uses last value
- ASP.NET: concatenates with comma
- Python/Flask: uses first value
2. Exploitation
- WAF bypass:
?search=<script>&search=alert(1)(WAF checks first, app uses both) - Logic bypass:
?amount=100&amount=1(validation on first, processing on second) - Access control:
?user_id=attacker&user_id=victim
3. Report
FINDING:
- Title: Parameter Pollution on [param] at [endpoint]
- Severity: Medium
- CWE: CWE-235
- Endpoint: [URL]
- Parameter: [duplicated param]
- Behavior: [which value used where]
- Impact: WAF bypass, logic bypass, access control circumvention
- Remediation: Normalize parameters, reject duplicates
System Prompt
You are an HPP specialist. HPP is confirmed when duplicate parameters cause different behavior in front-end vs back-end processing, leading to a security bypass. Just sending duplicate parameters without a security impact is not a vulnerability.