dbcve.org
RancherApplication · Suse

CVE-2023-22648

HIGH · 8.8 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 →
94/100
Remediation priority · Urgent
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 Improper Privilege Management vulnerability in SUSE Rancher causes permission changes in Azure AD not to be reflected to users while they are logged in the Rancher UI. This would cause the users to retain their previous permissions in Rancher, even if they change groups on Azure AD, for example, to a lower privileged group, or are removed from a group, thus retaining their access to Rancher instead of losing it. This issue affects Rancher: from >= 2.6.7 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

SUSE Rancher fails to refresh Azure AD group memberships during active UI sessions, causing users who are removed from or demoted in Azure AD groups to retain their previous higher privileges in Rancher. This improper privilege management allows continued access despite authoritative identity source changes.

MitigationUpgrade Rancher to version 2.6.13 or 2.7.4 or later to receive the patch, or implement forced re-authentication sessions to trigger periodic group membership re-validation from Azure AD.

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.7, < 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 installed Rancher version
    Run 'kubectl get rancher -n cattle-system -o jsonpath="{.items[0].status.version}"' or check the Rancher UI footer for the version number
    Affected if The installed version is >= 2.6.7 and < 2.6.13, OR >= 2.7.0 and < 2.7.4
  2. Confirm Azure AD authentication is configured
    In Rancher UI, go to Users > Authentication > Azure AD and verify a provider is enabled and configured with group sync settings
    Affected if Azure AD authentication is active and group synchronization is configured in Rancher
  3. Check for active user sessions
    Run 'kubectl get users -o name' to list all users, then inspect specific users with 'kubectl get user <username> -o yaml' to view their group memberships and last login timestamps
    Affected if Users exist with Azure AD group memberships that were synchronized and have active or recent sessions
  4. Review role bindings for users with Azure AD groups
    Run 'kubectl get clusterrolebindings -o wide' and 'kubectl get rolebindings -n cattle-system -o wide' to identify which users are bound to roles derived from Azure AD groups
    Affected if Role bindings exist for users whose group membership in Azure AD may have changed but whose Rancher access has not been revalidated

You are affected if your Rancher version falls within 2.6.7-2.6.12 or 2.7.0-2.7.3, Azure AD authentication is enabled, and users have active sessions where their group memberships may have changed in Azure AD but have not been re-validated in Rancher.

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 or 2.7.4 or later to receive the patch, or implement forced re-authentication sessions to trigger periodic group membership re-validation from Azure AD.

Recommended fix High confidence

Rancher 2.6.13 or 2.7.4

  1. Backup your Rancher environment before upgrading
  2. Identify your current Rancher version (2.6.x or 2.7.x)
  3. If running Rancher 2.6.7-2.6.12, upgrade to version 2.6.13
  4. If running Rancher 2.7.0-2.7.3, upgrade to version 2.7.4
  5. Follow the standard Rancher upgrade procedure for your deployment method
  6. After upgrade, verify that Azure AD group membership changes are now properly reflected in Rancher UI
Caveat Check Rancher release notes for any breaking changes between your current version and target version

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
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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