Description
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.
Analysis and contextual insights are available on OpenCVE Cloud.
Remediation
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
Advisories
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2021-1212 | 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. |
Github GHSA |
GHSA-w73w-5m7g-f7qc | Authorization bypass in github.com/dgrijalva/jwt-go |
References
History
No history.
Status: PUBLISHED
Assigner: mitre
Published:
Updated: 2024-08-04T15:49:07.136Z
Reserved: 2020-09-30T00:00:00.000Z
Link: CVE-2020-26160
No data.
Status : Modified
Published: 2020-09-30T18:15:27.397
Modified: 2024-11-21T05:19:24.290
Link: CVE-2020-26160
OpenCVE Enrichment
No data.
EUVD
Github GHSA