invalid start byte for kubiscan -rp about kubiscan HOT 4 CLOSED

works now. thanks!

from kubiscan.

Seems that some JWT token contains a 0x82 and the "utf-8" doesn't like it.

You can add "print (decoded_data)" between line 6 to line 7 here:

It should print the decoded token before the decoding to UTF-8 and you can share it here if it is not sensitive.
But the problem is probably because the data contains 0x82 byte.

Easy solution is that I will ignore that errors but it will give you the token without the 0x82 byte.
Another solution is that I will print it in bytes if it fails.

I will try to reproduce it and think about good solution, I will update.

from kubiscan.

@kbroughton Please check now, I fixed it and tested it.

from kubiscan.

Thanks for reporting :)

from kubiscan.