使い方
- インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
- 必要なツール、認証情報、対応環境を原文で確認します。
- 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/smartworldarafath/rea_skill --skill offensive-jwt開始前の確認
- 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
- スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。
JWT Implementation Security (offensive-jwt)
Authorization & Scope Notice: This skill is part of the REA_Skill + claude-red Unified Security & Reverse Engineering Suite. It is designed strictly for authorized security assessments, defensive architecture reviews, vulnerability triage, bug bounty verification, and remediation engineering on software, infrastructure, and assets you own or have explicit permission to test.
Overview
JSON Web Token (JWT) security assessment covering alg:none rejection, RS256-to-HS256 algorithm confusion, weak HMAC secret entropy, jwk/jku/x5u header injection, kid path/SQL injection, exp/nbf/aud/iss claim validation, and token revocation architecture. Use when auditing stateless authentication tokens.
Operational Workflow
- Surface & Architecture Inventory
- Identify all entrypoints, trust boundaries, parsers, and configuration files relevant to JWT Implementation Security (
authdomain). - Combine static code/binary inspection (via REA MCP tools,
rg, AST analysis, or decompilation) with runtime configuration verification.
- Hypothesis & Vulnerability Verification
- Test each security invariant systematically against known CWE and OWASP patterns.
- Record concrete evidence: affected file/procedure, line numbers or binary offsets, request/response trace, and root cause.
- Impact & Reachability Triage
- Evaluate whether the issue is reachable across trust boundaries, whether defense-in-depth controls mitigate it, and compute an accurate CVSS v3.1 / v4.0 score.
- Remediation & Regression Verification
- Implement or provide production-ready, copy-pasteable remediation code.
- Write an automated regression test or verification command to prove the flaw is resolved with 0 regressions.
Audit & Verification Checklist
| Phase | Check | Verification Method | Expected Secure State |
|---|---|---|---|
| 1. Discovery | Enumerate all auth surfaces and dependencies | Source search / REA binary & bundle inspection | Complete inventory of trust boundaries |
| 2. Input & State | Validate parser behavior, type safety, and state transitions | Boundary testing & static taint analysis | Strict schema validation and invariant checks |
| 3. Auth & Isolation | Verify caller identity, tenant isolation, and least privilege | Horizontal/vertical privilege matrix check | Explicit deny-by-default enforcement |
| 4. Defense-in-Depth | Inspect secondary controls, logging, and compiler/runtime flags | Config & header/binary flag audit | Full hardening and telemetry enabled |
| 5. Remediation | Apply fix and execute automated regression test | npm test / toolchain build & test suite | 0 vulnerabilities, 0 build errors |
Integration with REA MCP & Tooling
- Static & Binary Analysis: Pair with
rea-universal-orchestrator,rea-binary-disassembly,rea-web-bundle-recovery, orrea-mobile-app-recoverywhen source code is unavailable. - Interactive Scoping: Invoke
/rea-grill-mebefore large-scale assessments to clarify scope, target environments, and acceptance criteria. - Reporting: Pair with
offensive-reportingto format findings with CVSS vectors, CWE mappings, and remediation patches.