http-parameter-pollution은(는) 무엇을 하나요?
HTTP Parameter Pollution (HPP): 서버, 프록시, WAF, 애플리케이션 프레임워크가 중복된 쿼리/본문 키를 다르게 파싱합니다. 필터와 애플리케이션 계층이 어떤 값이 우선인지에 대해 불일치할 때 사용하여, 우회, SSRF 두 번째 URL, 논리 악용, CSRF 토큰 혼동을 가능하게 합니다.
HTTP 파라미터 오염 (HPP): 서버, 프록시, WAF, 애플리케이션 프레임워크가 중복된 쿼리/본문 키를 다르게 파싱합니다. 필터와 애플리케이션 계층이 어떤 값이 우선인지에 대해 불일치할 때 사용하여, 우회, SSRF 두 번째 URL, 논리 악용, CSRF 토큰 혼동을 가능하게 합니다.
이 스킬은 HTTP Parameter Pollution (HPP) 취약점을 악용하기 위한 전문 도구입니다. 서로 다른 웹 구성 요소(서버, 프록시, WAF, 프레임워크 등)가 중복된 HTTP 파라미터(쿼리 문자열 또는 요청 본문)를 처리하는 방식의 차이를 이용하여 보안 조치를 우회하거나 애플리케이션 로직을 오작동시킵니다. 주로 보안 필터와 백엔드 애플리케이션 간의 파싱 차이를 통해 SSRF(Server-Side Request Forgery) 공격, 인증 우회, CSRF 토큰 혼동 등을 유발하는 데 사용됩니다. 이 스킬은 Python 기반의 yaklang 플랫폼에서 사용하도록 설계되었으며, 다양한 HTTP 클라이언트 라이브러리(예: requests, httpx)와 호환됩니다. 스킬의 작동 방식은 대상 URL에 의도적으로 중복된 파라미터를 포함한 요청을 보내고, 각 구성 요소의 응답 차이를 분석하여 취약점을 탐지합니다. 이를 통해 개발자와 보안 연구원은 웹 애플리케이션의 안전성을 평가하고, 잠재적인 보안 위협을 사전에 식별할 수 있습니다.
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 Parameter Pollution (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.