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.

Sign up for GitHub

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

Jump to bottom

CVE-2020-26160 #9

Closed
comet-volterra opened this issue May 24, 2022 · 0 comments
Closed

CVE-2020-26160 #9

comet-volterra opened this issue May 24, 2022 · 0 comments
Labels
fixed the issue/bug had been fixed

Comments

@comet-volterra
Copy link

Describe the bug
jwt-go before 4.0.0-preview1 allows attackers to bypass intended access restrictions in situations with []string{} for m["aud"] (which is allowed by the specification). Because the type assertion fails, "" is the value of aud. This is a security problem if the JWT token is presented to a service that lacks its own audience check.

To Reproduce
Steps to reproduce the behavior:

  1. Go to '...'

Expected behavior
Ensure fix is present: dgrijalva/jwt-go#426
@myf5 myf5 added help wanted Extra attention is needed processing Identified, is working on it fixed the issue/bug had been fixed and removed help wanted Extra attention is needed processing Identified, is working on it labels May 31, 2022
@myf5 myf5 closed this as completed Jun 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
fixed the issue/bug had been fixed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@myf5 @comet-volterra