dbcve.org
RancherApplication · Suse

CVE-2022-43760

HIGH · 8.4 CVSS v3.1 Published 2023-06-01
Fix available
A fix is available. Upgrade to 2.6.13 / 2.7.4 or later.
See remediation →
88/100
Remediation priority · High
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
An Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in SUSE Rancher allows users in some higher-privileged groups to to inject code that is executed within another user's browser, allowing the attacker to steal sensitive information, manipulate web content, or perform other malicious activities on behalf of the victims. This could result in a user with write access to the affected areas being able to act on behalf of an administrator, once an administrator opens the affected web page. This issue affects Rancher: from >= 2.6.0 before < 2.6.13, from >= 2.7.0 before < 2.7.4.

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

Stored XSS vulnerability in SUSE Rancher allows authenticated users in higher-privileged groups to inject malicious JavaScript into web pages. When administrators view the affected pages, the injected code executes in their browsers, enabling session hijacking, credential theft, or actions performed on behalf of administrators.

MitigationUpgrade Rancher to version 2.6.13+, 2.7.4+, or later. If immediate upgrade is not possible, restrict write access to affected areas and monitor for suspicious user activity.

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.6.0, < 2.6.13>= 2.7.0, < 2.7.4

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/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 installed Rancher version
    Run 'helm list -n cattle-system' or check the Rancher UI under 'About' section to view the exact version number
    Affected if Version is >= 2.6.0 and < 2.6.13, OR >= 2.7.0 and < 2.7.4
  2. Confirm multi-user authentication is enabled
    Check if Rancher is configured with external authentication (e.g., LDAP, Active Directory, Okta) or local users with multiple accounts. Inspect Settings > Authentication in the Rancher UI
    Affected if Multiple non-admin users or groups have access to the Rancher environment
  3. Identify if lower-privileged users can create or modify resources
    Review user roles and role bindings in Rancher. Check if standard users or custom roles with write access exist. Go to Users > Authentication and Users & Groups sections
    Affected if Non-administrator users have write permissions to any resource that administrators view
  4. Inspect for suspicious stored scripts in user-editable fields
    Review custom group names, project descriptions, or other user-supplied text fields that appear in admin-viewable pages. Check Rancher logs and API responses for encoded script tags
    Affected if Any user-provided text fields contain unsanitized HTML or JavaScript content visible to administrators

A user is affected if Rancher version is within 2.6.0-2.6.12 or 2.7.0-2.7.3 AND multiple users with different privilege levels access the system with the ability to modify fields that administrators view.

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.6.13 / 2.7.4 or later
Fixed in 2.6.132.7.4
Interim mitigation

Upgrade Rancher to version 2.6.13+, 2.7.4+, or later. If immediate upgrade is not possible, restrict write access to affected areas and monitor for suspicious user activity.

Recommended fix High confidence

Rancher 2.6.13 or 2.7.4 (depending on your current minor branch)

  1. 1. Back up the Rancher environment (Rancher Manager UI, etcd database, Kubernetes cluster state)
  2. 2. Take a snapshot of the downstream clusters as a precaution
  3. 3. For Rancher deployed via Docker: Stop the current Rancher container and start a new container with the fixed version tag (2.6.13 or 2.7.4)
  4. 4. For Rancher deployed via Helm (RKE2/K3s): Update the Rancher Helm chart to use the fixed version and run `helm upgrade`
  5. 5. Wait for Rancher pods to restart and become healthy
  6. 6. Verify the upgrade by logging into the Rancher UI and confirming the version
  7. 7. Test that the XSS vulnerability is no longer exploitable by attempting to inject script content in the affected input fields
Caveat Minor version upgrades (e.g., 2.6.x to 2.7.x) may have breaking changes; patch upgrades within the same minor version (e.g., 2.6.12 to 2.6.13) typically do not

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
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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