jndi-injection은(는) 무엇을 하나요?
JNDI 인젝션 플레이북. Log4j2, Spring 또는 InitialContext.lookup()에 도달하는 모든 코드 경로를 통해 Java 애플리케이션이 공격자 제어 이름으로 JNDI 조회를 수행할 때 사용합니다.
JNDI 인젝션 플레이북. Log4j2, Spring 또는 InitialContext.lookup()에 도달하는 모든 코드 경로를 통해 Java 애플리케이션이 공격자 제어 이름으로 JNDI 조회를 수행할 때 사용합니다.
이 스킬은 JNDI 인젝션 공격에 대한 전문적인 플레이북으로, Java 애플리케이션에서 발생할 수 있는 JNDI 조회 취약점을 탐지하고 악용하는 방법을 제공합니다. 주요 대상은 Log4j2, Spring Framework, 또는 `InitialContext.lookup()`을 호출하는 기타 Java 코드 경로입니다. JNDI 인젝션은 공격자가 제어하는 이름을 애플리케이션이 신뢰할 수 없는 출처에서 조회할 때 발생하며, 원격 코드 실행(RCE)을 초래할 수 있습니다. 이 스킬은 CVE-2021-44228(Log4Shell)과 같은 알려진 취약점을 포함한 다양한 JNDI 인젝션 시나리오를 다루며, 보안 연구원, 침투 테스터, 그리고 개발자가 자신의 코드에서 이러한 위험을 식별하고 완화하는 데 도움을 줍니다. 교차 플랫폼 지원을 염두에 두고 설계되었으며, Yaklang 스크립팅 언어를 기반으로 합니다.
npx skills add https://github.com/yaklang/hack-skills/tree/main/skills/jndi-injectionInstalled? Explore more 코딩 & 개발 skills: steipete/bluebubbles, steipete/eightctl, steipete/blucli · View all 6 →
JNDI 인젝션 플레이북. Log4j2, Spring 또는 InitialContext.lookup()에 도달하는 모든 코드 경로를 통해 Java 애플리케이션이 공격자 제어 이름으로 JNDI 조회를 수행할 때 사용합니다.
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.