CVE-2021-3127Published Mar 16, 2021 · Mar 16Updated Oct 24
nats-io/jwt not enforcing checking of Import token permissions
High7.5Fix available
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/nats-io/jwt Go |
|
|
| github.com/nats-io/jwt/v2 Go |
|
|
| Product | Affected | Fixed in |
|---|---|---|
| github.com/nats-io/jwt Go |
|
|
| github.com/nats-io/jwt/v2 Go |
|
|
| github.com/nats-io/nats-server/v2 Go |
|
|
NATS Server 2.x before 2.2.0 and JWT library before 2.0.1 have Incorrect Access Control because Import Token bindings are mishandled.
From the CVE record · mitre
NATS Server 2.x before 2.2.0 and the JWT library before 2.0.1 mishandle Import Token bindings, resulting in incorrect access control. The input does not specify what an attacker can do, whether access is network or local, or whether authentication or user interaction is required.
Engineers running NATS Server 2.x before 2.2.0 or using Go packages github.com/nats-io/jwt before 1.2.3-0.20210314221642-a826c77dc9d2 or github.com/nats-io/jwt/v2 before 2.0.1 should check their dependencies.