CVE-2020-26160: Improper Handling of Exceptional Conditions
(updated )
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.
References
- github.com/advisories/GHSA-w73w-5m7g-f7qc
- github.com/dgrijalva/jwt-go/commit/ec0a89a131e3e8567adcb21254a5cd20a70ea4ab
- github.com/dgrijalva/jwt-go/issues/422
- github.com/dgrijalva/jwt-go/issues/462
- github.com/dgrijalva/jwt-go/pull/426
- nvd.nist.gov/vuln/detail/CVE-2020-26160
- pkg.go.dev/vuln/GO-2020-0017
- snyk.io/vuln/SNYK-GOLANG-GITHUBCOMDGRIJALVAJWTGO-596515
Code Behaviors & Features
Detect and mitigate CVE-2020-26160 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Dependency Scanning using SBOM also detects vulnerabilities from proprietary advisories that this site does not include. Learn more about Dependency Scanning using SBOM →