Authorization bypass in github.com/dgrijalva/jwt-go
jwt-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
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2020-26160US | high7.5 | Exploit | ||
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… | ||||
02
references
External citations — patches, advisories, analysis.
- https://github.com/dgrijalva/jwt-goPACKAGE
- https://github.com/dgrijalva/jwt-go/commit/ec0a89a131e3e8567adcb21254a5cd20a70ea4abWEB
- https://github.com/dgrijalva/jwt-go/issues/422WEB
- https://github.com/dgrijalva/jwt-go/issues/462WEB
- https://github.com/dgrijalva/jwt-go/pull/426WEB
- https://nvd.nist.gov/vuln/detail/CVE-2020-26160ADVISORY
- https://pkg.go.dev/vuln/GO-2020-0017WEB
- https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMDGRIJALVAJWTGO-596515WEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan