Skip to content

Authorization bypass in github.com/dgrijalva/jwt-go

High severity GitHub Reviewed Published May 18, 2021 to the GitHub Advisory Database • Updated May 20, 2024

Package

gomod github.com/dgrijalva/jwt-go (Go)

Affected versions

>= 0.0.0-20150717181359-44718f8a89b0, <= 3.2.0

Patched versions

None
gomod github.com/dgrijalva/jwt-go/v4 (Go)
< 4.0.0-preview1
4.0.0-preview1

Description

jwt-go 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. There is no patch available and users of jwt-go are advised to migrate to golang-jwt at version 3.2.1

References

Published by the National Vulnerability Database Sep 30, 2020
Reviewed May 18, 2021
Published to the GitHub Advisory Database May 18, 2021
Last updated May 20, 2024

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS score

0.193%
(58th percentile)

Weaknesses

CVE ID

CVE-2020-26160

GHSA ID

GHSA-w73w-5m7g-f7qc

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.