CVE-2020-26160
Jwt-go Project Jwt-go vulnerability
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.
Affected products
Jwt-go. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Jwt-go Project Jwt-go runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/dgrijalva/jwt-go/pull/426 · Patch
- snyk.io/vuln/SNYK-GOLANG-GITHUBCOMDGRIJALVAJWTGO-596515 · Third Party Advisory
- nvd.nist.gov/vuln/detail/CVE-2020-26160
- github.com/dgrijalva/jwt-go/issues/422
- github.com/dgrijalva/jwt-go/issues/462
- github.com/dgrijalva/jwt-go/commit/ec0a89a131e3e8567adcb21254a5cd20a70ea4ab
- pkg.go.dev/vuln/GO-2020-0017
- github.com/advisories/GHSA-w73w-5m7g-f7qc
- nvd.nist.gov/vuln/detail/CVE-2020-26160
- cve.org/CVERecord?id=CVE-2020-26160
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.