n/a · Vulnerability
cve-program · CVE-2020-26160
Publishedjwt-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.
Read the publisher's advisoryeuvd · EUVD-2021-1212
Publishedjwt-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.
Read the publisher's advisorynvd · CVE-2020-26160
Publishedjwt-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.
Read the publisher's advisoryosv · GHSA-w73w-5m7g-f7qc
Publishedjwt-go 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. There is no patch available and users of jwt-go are advised to migrate to [golang-jwt](https://github.com/golang-jwt/jwt) at version 3.2.1
Read the publisher's advisoryosv · GO-2020-0017
PublishedIf a JWT contains an audience claim with an array of strings, rather than a single string, and MapClaims.VerifyAudience is called with req set to false, then audience verification will be bypassed, allowing an invalid set of audiences to be provided.
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2020-26160 · CVE overview and exploitation status
SNYK-GOLANG-GITHUBCOMDGRIJALVAJWTGO-596515
cve-program · CVE-2020-26160
- https://github.com/dgrijalva/jwt-go/pull/426
- https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMDGRIJALVAJWTGO-596515
euvd · EUVD-2021-1212
- https://github.com/dgrijalva/jwt-go/pull/426
- https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMDGRIJALVAJWTGO-596515
nvd · CVE-2020-26160
- https://github.com/dgrijalva/jwt-go/pull/426
- https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMDGRIJALVAJWTGO-596515
osv · GHSA-w73w-5m7g-f7qc
- https://nvd.nist.gov/vuln/detail/CVE-2020-26160
- https://github.com/dgrijalva/jwt-go/issues/422
- https://github.com/dgrijalva/jwt-go/issues/462
- https://github.com/dgrijalva/jwt-go/pull/426
- https://github.com/dgrijalva/jwt-go/commit/ec0a89a131e3e8567adcb21254a5cd20a70ea4ab
- https://github.com/dgrijalva/jwt-go
- https://pkg.go.dev/vuln/GO-2020-0017
- https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMDGRIJALVAJWTGO-596515
osv · GO-2020-0017
Related changes
Linked by CVE identifierNo related changes are available here.