n/a · Vulnerability
cve-program · CVE-2020-26892
PublishedThe JWT library in NATS nats-server before 2.1.9 has Incorrect Access Control because of how expired credentials are handled.
Read the publisher's advisoryeuvd · EUVD-2022-0821
PublishedThe JWT library in NATS nats-server before 2.1.9 has Incorrect Access Control because of how expired credentials are handled.
Read the publisher's advisorynvd · CVE-2020-26892
PublishedThe JWT library in NATS nats-server before 2.1.9 has Incorrect Access Control because of how expired credentials are handled.
Read the publisher's advisoryosv · GHSA-2c64-vj8g-vwrq
Published(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.
Read the publisher's advisoryosv · GHSA-4w5x-x539-ppf5
Published## 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.
Read the publisher's advisoryosv · GO-2022-0380
PublishedThe 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.
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2020-26892 · CVE overview and exploitation status
cve-program · CVE-2020-26892
- https://github.com/nats-io/nats-server/commits/master
- https://www.openwall.com/lists/oss-security/2020/11/02/2
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/VT67XCLIIBYRT762SVFBYFFTQFVSM3SI/
euvd · EUVD-2022-0821
- https://github.com/nats-io/nats-server/commits/master
- https://www.openwall.com/lists/oss-security/2020/11/02/2
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/VT67XCLIIBYRT762SVFBYFFTQFVSM3SI/
nvd · CVE-2020-26892
- https://github.com/nats-io/nats-server/commits/master
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/VT67XCLIIBYRT762SVFBYFFTQFVSM3SI/
- https://www.openwall.com/lists/oss-security/2020/11/02/2
osv · GHSA-2c64-vj8g-vwrq
- https://github.com/nats-io/nats-server/security/advisories/GHSA-2c64-vj8g-vwrq
- https://github.com/nats-io/jwt/commit/e11ce317263cef69619fc1ca743b195d02aa1d8a
- https://advisories.nats.io/CVE/CVE-2020-26892.txt
- https://github.com/nats-io/nats-server
osv · GHSA-4w5x-x539-ppf5
- https://github.com/nats-io/jwt/security/advisories/GHSA-4w5x-x539-ppf5
- https://nvd.nist.gov/vuln/detail/CVE-2020-26892
- https://github.com/nats-io/jwt/commit/e11ce317263cef69619fc1ca743b195d02aa1d8a
- https://github.com/nats-io/nats-server/commit/1e08b67f08e18cd844dce833a265aaa72500a12f
- https://advisories.nats.io/CVE/CVE-2020-26892.txt
- https://github.com/nats-io/jwt
- https://github.com/nats-io/nats-server/commits/master
- https://lists.fedoraproject.org/archives/list/[email protected]/message/VT67XCLIIBYRT762SVFBYFFTQFVSM3SI
- https://pkg.go.dev/vuln/GO-2022-0380
- https://www.openwall.com/lists/oss-security/2020/11/02/2
osv · GO-2022-0380
Related changes
Linked by CVE identifierNo related changes are available here.