Ubuntu.comUB:CVE-2020-26160CVE-2020-26160
5 Medium
CVSS2
Attack Vector
NETWORK
Attack Complexity
LOW
Authentication
NONE
Confidentiality Impact
PARTIAL
Integrity Impact
NONE
Availability Impact
NONE
AV:N/AC:L/Au:N/C:P/I:N/A:N
7.5 High
CVSS3
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality Impact
HIGH
Integrity Impact
NONE
Availability Impact
NONE
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
0.002 Low
EPSS
Percentile
57.0%
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.
Bugs
- <https://github.com/dgrijalva/jwt-go/issues/422>
- <https://github.com/dgrijalva/jwt-go/issues/428>
- <http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971556>
Notes
| Author | Note |
|---|---|
| mdeslaur | as of 2020-10-02, the proposed patches have not been accepted into the upstream tree. juju-core doesn’t use jwt-go in a way that exposes the vulnerability |
Related
5 Medium
CVSS2
Attack Vector
NETWORK
Attack Complexity
LOW
Authentication
NONE
Confidentiality Impact
PARTIAL
Integrity Impact
NONE
Availability Impact
NONE
AV:N/AC:L/Au:N/C:P/I:N/A:N
7.5 High
CVSS3
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality Impact
HIGH
Integrity Impact
NONE
Availability Impact
NONE
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
0.002 Low
EPSS
Percentile
57.0%