github.com/nats-io/nats-server/v2
Affected
- introduced
0, fixed2.1.9(semver)
Fixed versions
2.1.9
Fix
- Fixed version
2.1.9go get github.com/nats-io/nats-server/[email protected]
Advisory
Also known as: CVE-2020-26892, GHSA-4w5x-x539-ppf5, GO-2022-0380
Incorrect handling of credential expiry by /nats-io/nats-server
(This advisory is canonically https://advisories.nats.io/CVE/CVE-2020-26892.txt )
Problem Description
NATS nats-server through 2020-10-07 has Incorrect Access Control because of how expired credentials are handled.
The NATS accounts system has expiration timestamps on credentials; the https://github.com/nats-io/jwt library had an API which encouraged misuse and an IsRevoked() method which misused its own API.
A new IsClaimRevoked() method has correct handling and the nats-server has been updated to use this. The old IsRevoked() method now always returns true and other client code will have to be updated to avoid calling it.
The CVE identifier should cover any application using the old JWT API, where the nats-server is one of those applications.
Affected versions
JWT library
NATS Server
Impact
Time-based credential expiry did not work.
Workaround
Have credentials which only expire after fixes can be deployed.
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 2.1.9 (semver)2.1.9
2.1.9go get github.com/nats-io/nats-server/[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