JWT browser and request evidence

Follow one synthetic token across the browser and HTTP request surface.

These paired cases demonstrate browser-storage discovery and exact Authorization, cookie, form and nested-JSON request carriers. The separate nested-JSON exploit case shows why a weak signing key matters. All tokens are synthetic.

JWT attack labs

Five different verification questions

PTK's JWT documentation names these five families. A working target is not a confirmed PTK finding; the mode and evidence for each case must be checked separately.

Target works · PTK finding pending

None algorithm

Unsigned synthetic token: HTTP 200 on vulnerable, 401 on repaired.

Open lab
Target works · manual Full proof pending

Algorithm/key confusion

Public RSA bytes used as an HMAC key grant synthetic admin only on the vulnerable route.

Open lab
Target works · manual Full proof pending

Weak HMAC secret

A forged nested-JSON JWT succeeds with the weak key, not the repaired strong key.

Open lab
Target works · manual Full proof pending

Null signature

Distinct from alg:none: HS256 with an empty signature succeeds only on the vulnerable route.

Open lab
Target works · manual Full proof pending

JWK header injection

The vulnerable verifier trusts a bounded embedded public JWK; the repaired route pins its own key.

Open lab

Static hosting

JWT discovery in browser state

Open the review page, then open the PTK JWT tool. Compare it with the clean control on the same origin.

Review

Cookie and Web Storage tokens

Seeds synthetic JWTs in a readable cookie, localStorage and sessionStorage.

Open storage review
Control

Opaque session values

Runs the same storage workflow with non-JWT values and clears review tokens first.

Open storage control

Local runtime

JWTs in captured requests

Generate one bounded request at a time using Authorization, an HttpOnly cookie, a form field or a nested JSON property.

DAST

Four exact request carriers

Each vulnerable endpoint has a paired control with the same method, token and browser action.

Open local DAST cases
Exploit case

Nested JSON weak-secret JWT

Issue a user token, inspect and re-sign it, then compare admin authorization with the strong-key control.

Open nested JSON case
PTK Pro · Coming soon

Advanced verification behavior

The same open fixtures also model algorithm-none, empty-signature, key-path and remote-key metadata handling without exposing private scanner rules.

Review advanced cases