dbcve.org
RancherApplication · Suse

CVE-2022-21951

MEDIUM · 6.8 CVSS v3.1 Published 2022-05-25
Fix available
A fix is available. Upgrade to 2.5.14 / 2.6.5 or later.
See remediation →
74/100
Remediation priority · Elevated
Public exploit Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A Cleartext Transmission of Sensitive Information vulnerability in SUSE Rancher, Rancher allows attackers on the network to read and change network data due to missing encryption of data transmitted via the network when a cluster is created from an RKE template with the CNI value overridden This issue affects: SUSE Rancher Rancher versions prior to 2.5.14; Rancher versions prior to 2.6.5.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis
How this class of weakness works · CWE-319

Sensitive information is transmitted over an unencrypted channel, so anyone positioned on the network path can read it as it passes. Credentials, tokens, and personal data are the usual casualties. The fix is to encrypt everything sensitive in transit with TLS and to remove any plaintext fallback.

General guidance for the cleartext transmission class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
RancherApplication
Affected:>= 2.5.0, < 2.5.14>= 2.6.0, < 2.6.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.5.14 / 2.6.5 or later
Fixed in 2.5.142.6.5
Recommended fix High confidence

Rancher 2.5.14 or 2.6.5 (upgrade to the latest 2.5.x or 2.6.x release respectively)

  1. 1. Backup your Rancher installation and all important data before proceeding with the upgrade.
  2. 2. For Rancher 2.5.x installations: Upgrade to Rancher version 2.5.14 or later.
  3. 3. For Rancher 2.6.x installations: Upgrade to Rancher version 2.6.5 or later.
  4. 4. Use the official Rancher upgrade documentation for your deployment method (Docker single-node or Kubernetes cluster).
  5. 5. For Docker single-node upgrade: Stop the current container, then start a new container with the new image tag using the same persistent data volume.
  6. 6. For Kubernetes-based upgrade: Update the Helm chart repository, then run 'helm upgrade' with the new chart version.
  7. 7. After upgrade, verify that Rancher is functioning correctly and all clusters are accessible.
  8. 8. When creating new clusters from RKE templates after upgrade, verify that network data is now encrypted during transmission.

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-21951 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-21951 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data