(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
* all versions prior to 1.1.0
* fixed after nats-io/jwt PR 103 landed (2020-10-06)
#### NATS Server
* Version 2 prior to 2.1.9
+ 2.0.0 through and including 2.1.8 are vulnerable.
* fixed with nats-io/nats-server PRs 1632, 1635, 1645
## 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.
## 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
* all versions prior to 1.1.0
* fixed after nats-io/jwt PR 103 landed (2020-10-06)
#### NATS Server
* Version 2 prior to 2.1.9
+ 2.0.0 through and including 2.1.8 are vulnerable.
* fixed with nats-io/nats-server PRs 1632, 1635, 1645
## 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.
The AccountClaims.IsRevoked and Export.IsRevoked functions improperly validate expired credentials using the current system time rather than the issue time of the JWT to be tested.
These functions cannot be used properly. Newer versions of the jwt package provide an IsClaimRevoked method which performs correct validation. In these versions, the IsRevoked method always return true.
EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.
Original publisher date fields
datePublished: Nov 6, 2020, 7:36:45 AM
dateUpdated: Aug 4, 2024, 4:03:22 PM
No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.
NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
The original JSON retains the logical configuration operators, exclusions and version bounds.
No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.