http-parameter-pollution 是做什麼的？
HTTP 參數污染 (HPP)：利用伺服器、代理伺服器、WAF 與應用程式框架對重複查詢/主體鍵值解析方式不同。適用於過濾器與應用層對「哪個值會被採用」有歧義的情況，從而實現繞過、SSRF 第二層 URL、邏輯濫用或 CSRF 令牌混淆。
HTTP 參數污染 (HPP)：利用伺服器、代理伺服器、WAF 與應用程式框架對重複查詢/主體鍵值解析方式不同，繞過過濾器、實現 SSRF 第二層 URL、邏輯濫用或 CSRF 令牌混淆。
此技能專注於 HTTP 參數污染（HPP）漏洞的利用，這是一種利用不同 HTTP 層級（如代理伺服器、WAF、應用伺服器及框架）對重複鍵值參數解析不一致的攻擊技術。當安全過濾器與應用層在處理重複參數時，對「哪個值會被採用」的規則不同，即可繞過驗證機制。此技能適用於滲透測試、紅隊演練及安全審計場景，支援 yaklang 生態系統或獨立使用。主要用途包括：繞過 WAF 規則、實施 SSRF 攻擊的二次 URL 跳轉、邏輯濫用（如更改使用者權限或訂單金額），以及 CSRF 令牌混淆以繞過防護。其原理是透過建構多重參數（如 `?param=legit¶m=malicious`），利用不同元件在解析時選取不同值的特性，使攻擊向量能穿過過濾層抵達應用邏輯。此技能為開發者與安全研究人員提供了可自動化測試的標準化方法，有助於辨識與利用此類常見但不被重視的解析歧義漏洞。
npx skills add https://github.com/yaklang/hack-skills/tree/main/skills/http-parameter-pollutionInstalled? Explore more 程式設計與開發 skills: steipete/bluebubbles, steipete/eightctl, steipete/blucli · View all 6 →
HTTP 參數污染 (HPP)：利用伺服器、代理伺服器、WAF 與應用程式框架對重複查詢/主體鍵值解析方式不同。適用於過濾器與應用層對「哪個值會被採用」有歧義的情況，從而實現繞過、SSRF 第二層 URL、邏輯濫用或 CSRF 令牌混淆。
This repo contains 20 individual skills — each has its own dedicated page.
401/403 bypass playbook. Use when encountering access-denied responses on admin panels, API endpoints, or restricted paths. Covers path manipulation, HTTP method tampering, header injection, protocol downgrade, and automated bypass tools.
Active Directory ACL abuse playbook. Use when exploiting misconfigured AD permissions including GenericAll, WriteDACL, DCSync rights, shadow credentials, LAPS reading, GPO abuse, and BloodHound-guided attack paths.
AD Certificate Services attack playbook. Use when targeting misconfigured AD CS for privilege escalation via ESC1-ESC13 template abuse, NTLM relay to enrollment, CA officer abuse, and certificate-based persistence.
Kerberos attack playbook for Active Directory. Use when targeting AD authentication via AS-REP roasting, Kerberoasting, golden/silver/diamond tickets, delegation abuse, or pass-the-ticket attacks.
AI/ML security playbook. Use when assessing model supply chain attacks (pickle RCE, poisoned weights), adversarial examples, model poisoning, model stealing, data privacy attacks (membership inference, model inversion), and autonomous agent security risks.
Android pentesting playbook. Use when testing Android applications for SSL pinning bypass, exported component abuse, WebView vulnerabilities, intent redirection, root detection bypass, tapjacking, and backup extraction during authorized mobile security assessments.
Anti-debugging detection and bypass playbook. Use when reversing protected binaries that detect debuggers via ptrace, PEB flags, timing checks, or signal/exception handlers on Linux and Windows.
API authentication and JWT abuse playbook. Use when testing bearer tokens, API keys, claim trust, header spoofing, rate limits, and API auth boundary weaknesses.
API authorization and BOLA testing playbook. Use when APIs expose object identifiers, nested resources, hidden writable fields, or weak function-level authorization.
API reconnaissance and documentation review playbook. Use when discovering endpoints, schemas, versions, OpenAPI specs, hidden docs, and surface area for API testing.
Entry P1 category router for API security. Use when choosing between API recon, authorization, token abuse, and hidden-parameter workflows before any deeper API topic skill.
Arbitrary write to RCE playbook. Use when you have an arbitrary write primitive (from heap exploitation, format string, or OOB write) and need to convert it into code execution by targeting GOT, hooks, _IO_FILE vtable, exit_funcs, TLS_dtor_list, modprobe_path, .fini_array, or C++ vtables.
Authentication bypass testing playbook. Use when assessing login flows, password reset logic, account recovery, MFA bypass, token predictability, brute-force resistance, and session boundary flaws.
Entry P1 category router for authentication and authorization. Use when testing login flows, sessions, object authorization, JWT, OAuth, CORS, CSRF, and enterprise SSO weaknesses before any deeper auth topic skill.
Binary protection bypass playbook. Use when identifying and bypassing ASLR, PIE, NX/DEP, stack canary, RELRO, FORTIFY_SOURCE, CET, and MTE protections in ELF binaries to enable exploitation.
Browser and V8 exploitation playbook. Use when exploiting JavaScript engine vulnerabilities including JIT type confusion, incorrect bounds elimination, and V8 sandbox bypass to achieve renderer RCE and sandbox escape in Chrome/Chromium.
Entry P1 category router for business logic testing. Use when workflow abuse, race conditions, pricing flaws, or multi-step state attacks matter more than parser-level input injection.
Business logic vulnerability playbook. Use when reasoning about workflows, race conditions, price manipulation, coupon abuse, state machines, and multi-step authorization gaps.
Classical cipher analysis playbook. Use when encountering substitution ciphers, Vigenere, transposition, XOR, or encoded text in CTF challenges that requires frequency analysis, Kasiski examination, or known-plaintext cryptanalysis.
Clickjacking playbook. Use when testing whether target pages can be framed, whether X-Frame-Options or CSP frame-ancestors are properly configured, and whether UI redress attacks can trigger sensitive actions.
Send and manage iMessages via BlueBubbles, including attachments, tapbacks, edits, replies, and groups.
Control Eight Sleep pods (status, temperature, alarms, schedules).
BluOS CLI (blu) for discovery, playback, grouping, and volume.
Create, search, and manage Bear notes via grizzly CLI.
Capture frames or clips from RTSP/ONVIF cameras.
Search GIF providers with CLI/TUI, download results, and extract stills/sheets.