CVE-2020-26521: GO-2022-0402 - Panic in NATS JWT decoding in github.com/nats-io/jwt

CVE-2020-26521 · Severity: low · CVSS 3.1 · Published 2022-07-01

Panic in NATS JWT decoding in github.com/nats-io/jwt

Technologies: github.com/nats-io/jwt (Go), github.com/nats-io/nats-server/v2 (Go). Vendors: Go.

Quick answers

Is CVE-2020-26521 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2020-26521 being exploited in the wild.
How severe is CVE-2020-26521?
Low severity, with a CVSS score of 3.1, published 1 July 2022.
Which products and versions are affected?
github.com/nats-io/jwt (Go) SEMVER:introduced=0,fixed=1.1.0; github.com/nats-io/nats-server/v2 (Go) SEMVER:introduced=0,fixed=2.1.9.
Is there a fix for CVE-2020-26521?
Yes. github.com/nats-io/jwt (Go): upgrade to 1.1.0 or later; github.com/nats-io/nats-server/v2 (Go): upgrade to 2.1.9 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2020-26521?
Check whether you run github.com/nats-io/jwt (Go) or github.com/nats-io/nats-server/v2 (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/nats-io/jwt (Go): upgrade to 1.1.0 or later
    go get github.com/nats-io/jwt@v1.1.0
  • github.com/nats-io/nats-server/v2 (Go): upgrade to 2.1.9 or later
    go get github.com/nats-io/nats-server/v2@v2.1.9

Affected products

  • github.com/nats-io/jwt (Go) SEMVER:introduced=0,fixed=1.1.0
  • github.com/nats-io/nats-server/v2 (Go) SEMVER:introduced=0,fixed=2.1.9

Identifiers

  • CVE-2020-26521
  • GHSA-h2fg-54x9-5qhq
  • GHSA-hmm9-r2m2-qg9w
  • GO-2022-0402

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.