Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unsupported Type: undefined #38

Open
he4rtbleed opened this issue Aug 8, 2024 · 1 comment
Open

Unsupported Type: undefined #38

he4rtbleed opened this issue Aug 8, 2024 · 1 comment

Comments

@he4rtbleed
Copy link

The value of typ in the header of the jwt token may not exist, please add exception handling for this case.

@AmirhosseinBidokhti
Copy link

I got the same error trying to test this tool to solve a lab on Portswigger. Used -f to skip token validation but still raised error regarding the HMAC.

✗ jwt-cracker -t eyJraWQiOiIwNTRmM2RjZC1kY2E5LTRmNTQtYTY0ZS0yMzQ2ZjU4YjM1NzYiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJwb3J0c3dpZ2dlciIsImV4cCI6MTcyMzgyNjA3OSwic3ViIjoid2llbmVyIn0.9_FGsLMyxrwnRSGAiLtkq4KeIxGWWn_a9KTUfvQ0_GQ -d jwt.secrets.list -f

Unsupported Typ: undefined
node:internal/validators:162
throw new ERR_INVALID_ARG_TYPE(name, 'string', value);
^

TypeError [ERR_INVALID_ARG_TYPE]: The "hmac" argument must be of type string. Received undefined
at new NodeError (node:internal/errors:406:5)
...

Node.js v20.8.0
SECRET NOT FOUND
Time taken (sec): 0.081
Total attempts: 0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants