CVE-2020-26160 (High) detected in github.com/dgrijalva/jwt-go-v3.2.0

[mend-bolt-for-github]

CVE-2020-26160 - High Severity Vulnerability

Vulnerable Library - github.com/dgrijalva/jwt-go-v3.2.0

Golang implementation of JSON Web Tokens (JWT)

Dependency Hierarchy:

• ❌ github.com/dgrijalva/jwt-go-v3.2.0 (Vulnerable Library)

Found in HEAD commit: 86266a070a0504e2b0c6f3b89c04e1f472431af6

Found in base branch: master

Vulnerability Details

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.

Publish Date: 2020-09-30

URL: CVE-2020-26160

CVSS 3 Score Details (7.5)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: High
  • Integrity Impact: None
  • Availability Impact: None

For more information on CVSS3 Scores, click here.

---

Step up your Open Source Security Game with WhiteSource here

[bnfinet]

My initial take is that VP is not vulnerable...

"This is a security problem if the JWT token is presented to a service that lacks its own audience check."

/validate does include verifyUser()

I'll investigate further and confirm.

[bnfinet]

jwt-go has gone fallow. This discussion is trying to find the way forward...

dgrijalva/jwt-go#428

This fork has a fix
https://github.com/form3tech-oss/jwt-go

[bnfinet]

The VP side aud check was there, though I've cleaned up the check to make it more apparent.

[bnfinet]

merged in v0.21.0