Auth bypass in Jwt-Go Project
CVE-2020-26160
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.
Vulnerability class: Broken Authentication
Published · last modified .
CVSS v3 metric
CVSS v3 base score 7.5 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N.
EPSS exploit prediction
EPSS: 0.022 (81.5th percentile), scored .
Low probability of exploitation in the next 30 days, but still tracked. 82nd percentile — 81.5% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.022 · newest: 0.022 · change: 0.000
Affected products
Weakness classification (CWE)
Public proof-of-concept exploits
References
- github.com/dgrijalva/jwt-go/pull/426 (Patch, Third Party Advisory)
- snyk.io/vuln/SNYK-GOLANG-GITHUBCOMDGRIJALVAJWTGO-596515 (Third Party Advisory)
Frequently asked questions
- What is CVE-2020-26160?
- CVE-2020-26160 is a high-severity vulnerability in Jwt-Go Project, classified under Improper Authentication. CVSS score: 7.5/10. Published 2020-09-30.
- How severe is CVE-2020-26160?
- High severity. CVSS v3 base score is 7.5 out of 10.
- Is CVE-2020-26160 known to be exploited?
- 16 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.