Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
noorqureshi/web-auth-jwtWeb and bug bounty

web-auth-jwt

⁨Attack JWT/session authentication. Load when auth uses a JWT (three base64url parts, header.payload.signature), Authorization: Bearer, or you see alg/kid/jku fields. Signals: eyJ... tokens, "alg":"none"/"HS256"/"RS256", kid header, JWKS endpoints, role/admin claims.⁩

v2026.10.14-ee0e0c55 installs+5 in 7 days27 StarsMITsynced 22 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install noorqureshi/web-auth-jwt

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
v8N7+KAY1t…8zgGOgAw==The CLI checks the SHA-256 and the signature before it writes a file.
Packagea6b85e8e…d7897095
a6b85e8e1f43…6f56d78970953 files · ⁦3.9 KB⁩
ScanLow1 finding
  • Links to outside domains
See the full scan
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/web/web-auth-jwt@ee0e0c5

When it applies

The app authenticates with a JSON Web Token and trusts claims inside it (user id, role, isAdmin). The win is forging a valid-looking token the server accepts.

Why it works

JWTs are only as safe as their signature verification. Implementations routinely skip it, confuse algorithms, or trust attacker-controlled key hints (kid, jku, x5u). If you can make the server accept a signature you produced, you own every claim.

Method

Payloads & full variation set: cheatsheet.md next to this file — work the set, not the first line.

  1. Decode & read claims: jwt_tool <token> — look for role, admin, sub, weak exp.
  2. alg=none: strip the signature and set header {"alg":"none"}; some libs accept it.
  3. Algorithm confusion RS256→HS256: if the server verifies RS256 with the public key, re-sign HS256 using that public key as the HMAC secret — server verifies with the same key. jwt_tool -X k -pk public.pem.
  4. Weak HMAC secret: crack HS256 offline — hashcat -m 16500 token.txt rockyou.txt; if it falls, mint any token.
  5. kid / jku / x5u abuse: kid path traversal or SQLi to control the key file; jku/x5u pointing at your JWKS so the server fetches your public key and you sign with your private key.

Gotchas

  • Editing claims without re-signing fails unless verification is broken — confirm the vuln class first.
  • exp/nbf may be enforced even when signature isn't — keep timestamps valid.
  • Public key sourcing: grab it from /.well-known/jwks.json, a cert, or TLS if not published.

Verify success

Server accepts a token you forged with elevated claims (e.g. admin panel loads, or an authenticated endpoint returns another user's data with your minted sub).

References

PortSwigger JWT labs; jwt_tool wiki; Auth0 "Critical vulnerabilities in JWT libraries".

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsNoNo
Uses the networkYesYes
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

  1. InfoLink · Links to outside domains

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v2026.10.14-ee0e0c5Nov 13, 2026ee0e0c5a6b85e8eSigned–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login