Authorization bypass in github.com/dgrijalva/jwt-go
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/dgrijalva/jwt-go Go |
| No fix yet |
| github.com/dgrijalva/jwt-go/v4 Go |
|
|
| Product | Affected | Fixed in |
|---|---|---|
| github.com/dgrijalva/jwt-go Go |
| No fix yet |
| github.com/dgrijalva/jwt-go/v4 Go |
|
|
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.
From the CVE record · mitre
jwt-go can treat an empty-string-list JWT audience as an empty string when a type assertion fails. An attacker can bypass intended access restrictions by presenting such a token to a service that lacks its own audience check. The input does not specify whether prior authentication or user interaction is required.
Engineers using Go github.com/dgrijalva/jwt-go from 0.0.0-20150717181359-44718f8a89b0 through 3.2.0, or github.com/dgrijalva/jwt-go/v4 before 4.0.0-preview1, should check their services.