CVE-2018-20321: GO-2022-0644 - Access Control Bypass in github.com/rancher/rancher

CVE-2018-20321 · Severity: low · CVSS 3.1 · Published 2024-08-21

Access Control Bypass in github.com/rancher/rancher

Technologies: github.com/rancher/rancher (Go). Vendors: Go.

Quick answers

Is CVE-2018-20321 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2018-20321 being exploited in the wild.
How severe is CVE-2018-20321?
Low severity, with a CVSS score of 3.1, published 21 August 2024.
Which products and versions are affected?
github.com/rancher/rancher (Go) SEMVER:introduced=2.0.0,fixed=2.1.6, SEMVER:introduced=2.0.0+incompatible,fixed=2.1.6+incompatible.
Is there a fix for CVE-2018-20321?
Yes. github.com/rancher/rancher (Go): upgrade to 2.1.6, 2.1.6+incompatible or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2018-20321?
Check whether you run github.com/rancher/rancher (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/rancher/rancher (Go): upgrade to 2.1.6, 2.1.6+incompatible or later
    go get github.com/rancher/rancher@v2.1.6+incompatible

Affected products

  • github.com/rancher/rancher (Go) SEMVER:introduced=2.0.0,fixed=2.1.6, SEMVER:introduced=2.0.0+incompatible,fixed=2.1.6+incompatible

Identifiers

  • CVE-2018-20321
  • GHSA-9qq2-xhmc-h9qr
  • GO-2022-0644

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