CVE-2020-26160GHSA-W73W-5M7G-F7QCGO-2020-0017SNYK-GOLANG-GITHUBCOMDGRIJALVAJWTGO-596515
jwt-go before 4.0.0-preview1 allows attackers to bypass intended access restrictions in situations with []string{} for m["aud"] (which is al
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 4.0.0-preview1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 1 proof of concept on GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- n/a n/a
Version range not reported
- github.com/dgrijalva/jwt-goGo
From 0.0.0-20150717181359-44718f8a89b0 · through 3.2.0
- github.com/dgrijalva/jwt-go/v4Go
fixed in 4.0.0-preview1
- github.com/dgrijalva/jwt-goGo
From 0.0.0-20150717181359-44718f8a89b0