The JWT library in NATS nats-server before 2.1.9 allows a denial of service (a nil dereference in Go code).
euvd · EUVD-2022-1028 · Published
No access to your tenant or devices. Every item links to its source. What this means
The JWT library in NATS nats-server before 2.1.9 allows a denial of service (a nil dereference in Go code).
Read the publisher's advisoryThe JWT library in NATS nats-server before 2.1.9 allows a denial of service (a nil dereference in Go code).
Read the publisher's advisoryThe JWT library in NATS nats-server before 2.1.9 allows a denial of service (a nil dereference in Go code).
Read the publisher's advisory## 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 * all versions prior to 1.1.0 #### NATS Server * Version 2 prior to 2.1.9 ## Impact #### JWT library * Programs would nil dereference and panic, aborting execution by default. #### NATS server * Denial of Service caused by process termination ## 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.
Read the publisher's advisory(This advisory is canonically <https://advisories.nats.io/CVE/CVE-2020-26521.txt>) ## 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 * all versions prior to 1.1.0 #### NATS Server * Version 2 prior to 2.1.9 ## Impact #### JWT library * Programs would nil dereference and panic, aborting execution by default. #### NATS server * Denial of Service caused by process termination ## 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.
Read the publisher's advisoryA malicious account can create and sign a User JWT which causes a panic when decoded by the NATS JWT library.
Read the publisher's advisoryCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
Compare earlier KEV listings and EPSS scores. Advisory wording and affected versions have a separate history.
A prediction change is reported when EPSS rises from below 10% to 10% or higher. Every daily score change from the last 30 days stays in this history. Before that, it keeps KEV changes and moves between EPSS bands (0.1%, 1%, 5%, 10%, 20%, 50% and 90%).
See how the publisher's advisory changed over time. Each link opens the version saved at that time. The publisher's update date can differ from the date shown here.
Each link identifies one complete publisher record. History can include advisories that previously shared an identifier; an identifier removed by a publisher no longer establishes a current relationship. A historical link shows only that record and earlier saved versions. Failed checks and unchanged reads do not create new versions.
euvd · EUVD-2022-1028 · Published
euvd · EUVD-2022-1028 · Published
euvd · EUVD-2022-1028 · Published
euvd · EUVD-2022-1028 · Published
euvd · EUVD-2022-1028 · Published
euvd · EUVD-2022-1028 · Published
euvd · EUVD-2022-1028 · Published
euvd · EUVD-2022-1028 · Published
euvd · EUVD-2022-1028 · Published
euvd · EUVD-2022-1028 · Published
euvd · EUVD-2022-1028 · Published
euvd · EUVD-2022-1028 · Published
nvd · CVE-2020-26521 · Published
osv · GHSA-h2fg-54x9-5qhq · Published
osv · GHSA-hmm9-r2m2-qg9w · Published
osv · GO-2022-0402 · Published
cve-program · CVE-2020-26521 · Published