dbcve.org
RancherApplication · Suse

CVE-2022-43758

MEDIUM · 6.8 CVSS v3.1 Published 2023-02-07
Fix available
A fix is available. Upgrade to 2.5.17 / 2.6.10 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable

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 Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') vulnerability in SUSE Rancher allows code execution for user with the ability to add an untrusted Helm catalog or modifying the URL configuration used to download KDM (only admin users by default) This issue affects: SUSE Rancher Rancher versions prior to 2.5.17; Rancher versions prior to 2.6.10; Rancher versions prior to 2.7.1.

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 · high confidence

SUSE Rancher contains an OS Command Injection vulnerability where an authenticated administrator can execute arbitrary commands by adding a malicious Helm catalog or modifying the KDM download URL configuration. The vulnerability stems from improper neutralization of special elements in OS commands used during Helm chart repository processing and KubeDriver (KDM) manifest downloads.

MitigationUpgrade SUSE Rancher to version 2.5.17, 2.6.10, or 2.7.1 or later. Limit admin access to trusted personnel and audit Helm catalog configurations until patching is complete.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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.17>= 2.6.0, < 2.6.10>= 2.7.0, < 2.7.1

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
Low
Privileges
High
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Rancher version
    Log into the Rancher UI and navigate to the About page (usually via the user menu or bottom-left corner), or query the API endpoint /version, or run 'rancher --version' from the CLI if rancher binary is available
    Affected if The installed version falls within >= 2.5.0 and < 2.5.17, OR >= 2.6.0 and < 2.6.10, OR >= 2.7.0 and < 2.7.1
  2. Review Helm catalog configurations
    In Rancher UI, go to Apps > Managed Charts (or Catalogs in older versions). Via API, query /v1/catalog.cattle.io.clusterrepos. Inspect each catalog entry for any custom repository URLs
    Affected if Any Helm catalog repository URL contains shell metacharacters such as $, `, ;, |, or &&, or URLs that appear to embed commands
  3. Inspect KDM download URL settings
    Check Rancher global settings or cluster driver configuration for any KubeDriver (KDM) manifest URL fields. Look for settings named 'KDM URL' or similar under Rancher settings or provisioning configurations
    Affected if The KDM download URL contains suspicious characters like $, `, ;, |, &&, or other command injection patterns
  4. Audit admin user access
    Review the list of administrator accounts in Rancher (Users > Authentication > Local Users or Active Directory/LDAP if integrated). Check for any unauthorized or unexpected admin accounts
    Affected if There are untrusted or unknown administrator accounts that could have added malicious Helm catalogs or modified KDM settings

You are affected if your Rancher version is less than 2.5.17, 2.6.10, or 2.7.1 AND an authenticated admin has configured a malicious Helm catalog or modified the KDM URL with embedded shell commands.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.17 / 2.6.10 / 2.7.1 or later
Fixed in 2.5.172.6.102.7.1
Interim mitigation

Upgrade SUSE Rancher to version 2.5.17, 2.6.10, or 2.7.1 or later. Limit admin access to trusted personnel and audit Helm catalog configurations until patching is complete.

Recommended fix High confidence

Upgrade to Rancher 2.5.17, 2.6.10, or 2.7.1 (or later in respective release lines)

  1. 1. Review the current Rancher version by navigating to the Rancher UI and checking the version in the footer, or run 'kubectl get rancher -n cattle-system -o jsonpath='{.items[0].status.rancherVersion}'
  2. 2. Identify the appropriate upgrade path based on your current major.minor version (2.5.x → 2.5.17, 2.6.x → 2.6.10, or 2.7.x → 2.7.1)
  3. 3. Before upgrading, back up your Rancher environment following the official backup procedure
  4. 4. For Kubernetes-based installations: upgrade Rancher using Helm - run 'helm repo update' then 'helm upgrade rancher rancher-stable/rancher --version <target-version> --namespace cattle-system'
  5. 5. For Docker-based installations: stop the current container, then run the new container with the target version tag
  6. 6. After upgrade completes, verify Rancher is functional and the version matches the target fixed release
  7. 7. Confirm the vulnerability is resolved by ensuring users without admin privileges cannot perform Helm catalog operations
Caveat Review the release notes for the target version for any breaking changes or required migration steps before upgrading

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

Fix this in Rancher Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-43758 — 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-43758 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