-
-
Notifications
You must be signed in to change notification settings - Fork 253
Added active scanner for the JWT "None" Exploit #161
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
Conversation
Read more about the exploit here: https://www.sjoerdlangkemper.nl/2016/09/28/attacking-jwt-authentication/
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the contribution!
Edit: If you could address the two LGTM items as well that'd be wonderful (they're simple, just two lines missing var keyword).
|
@wg4568 do you plan to address the remaining comment? |
1 similar comment
|
@wg4568 do you plan to address the remaining comment? |
kingthorin
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks
|
Thanks! |
I wrote an active scanner rule to detect an exploit that arises from using poorly implemented JWT.
More info: https://www.sjoerdlangkemper.nl/2016/09/28/attacking-jwt-authentication/