github.com/nats-io/jwt
Affected
- introduced
0, fixed1.1.0(semver)
Fixed versions
1.1.0
Fix
- Fixed version
1.1.0go get github.com/nats-io/[email protected]
Advisory
Also known as: CVE-2020-26521, GHSA-hmm9-r2m2-qg9w, GO-2022-0402
Nil dereference in NATS JWT, DoS of nats-server
Problem Description
The NATS account system has an Operator trusted by the servers, which signs Accounts, and each Account can then create and sign Users within their account. The Operator should be able to safely issue Accounts to other entities which it does not fully trust.
A malicious Account could create and sign a User JWT with a state not created by the normal tooling, such that decoding by the NATS JWT library (written in Go) would attempt a nil dereference, aborting execution.
The NATS Server is known to be impacted by this.
Affected versions
JWT library
NATS Server
Impact
JWT library
NATS server
Workaround
If your NATS servers do not trust any accounts which are managed by untrusted entities, then malformed User credentials are unlikely to be encountered.
Solution
Upgrade the JWT dependency in any application using it.
Upgrade the NATS server if using NATS Accounts.
High Basis: The source's own band: HIGH
0, fixed 1.1.0 (semver)1.1.0
1.1.0go get github.com/nats-io/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0