dbcve.org
RancherApplication · Suse

CVE-2023-22649

MEDIUM · 6.5 CVSS v3.1 Published 2024-10-16
Fix available
A fix is available. Upgrade to 2.6.14 / 2.7.10 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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 vulnerability has been identified which may lead to sensitive data being leaked into Rancher's audit logs. [Rancher Audit Logging](https://ranchermanager.docs.rancher.com/how-to-guides/advanced-user-guides/enable-api-audit-log) is an opt-in feature, only deployments that have it enabled and have [AUDIT_LEVEL](https://ranchermanager.docs.rancher.com/how-to-guides/advanced-user-guides/enable-api-audit-log#audit-log-levels) set to `1 or above` are impacted by this issue.

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

Sensitive data is written to Rancher's audit logs when audit logging is enabled with AUDIT_LEVEL set to 1 or above, potentially exposing confidential information to unauthorized parties with log access.

MitigationReview audit logs for exposed sensitive data, and either disable audit logging if not required or upgrade to a patched version if available; consider adjusting AUDIT_LEVEL settings.

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.14>= 2.7.0, < 2.7.10>= 2.8.0, < 2.8.2

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

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

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. Check Rancher version
    In the Rancher UI, go to the bottom-left corner to view the version number, or run 'kubectl get rancher' in the system-global namespace
    Affected if the installed version falls within 2.6.0 to 2.6.13, 2.7.0 to 2.7.9, or 2.8.0 to 2.8.1
  2. Verify audit logging is enabled
    Check the Rancher audit log configuration, typically found in the Rancher settings or via the API at /v3/settings/audit-log-filename
    Affected if audit logging is enabled and audit log files are being generated
  3. Check AUDIT_LEVEL setting
    Query the AUDIT_LEVEL setting via the API at /v3/settings/audit-level or check the Rancher deployment environment variables
    Affected if AUDIT_LEVEL is set to 1, 2, or 3 (where 1=Metadata, 2=Request, 3=Request+Response)
  4. Inspect recent audit logs for sensitive data
    Locate and review recent audit log files for exposed credentials, tokens, or other sensitive information in request/response bodies
    Affected if sensitive data such as passwords, API tokens, or secrets appear in the audit logs

You are affected if your Rancher version is 2.6.0-2.6.13, 2.7.0-2.7.9, or 2.8.0-2.8.1 AND audit logging is enabled with AUDIT_LEVEL set to 1 or higher, with sensitive data visible in the logs.

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.14 / 2.7.10 / 2.8.2 or later
Fixed in 2.6.142.7.102.8.2
Interim mitigation

Review audit logs for exposed sensitive data, and either disable audit logging if not required or upgrade to a patched version if available; consider adjusting AUDIT_LEVEL settings.

Recommended fix High confidence

Rancher 2.6.14, 2.7.10, or 2.8.2 (select based on your current major.minor version)

  1. 1. Identify your current Rancher version by checking the Rancher UI (top-left corner) or the cluster's Kubernetes resources
  2. 2. Determine the appropriate target version based on your current major.minor version: if using 2.6.x, upgrade to 2.6.14 or later; if using 2.7.x, upgrade to 2.7.10 or later; if using 2.8.x, upgrade to 2.8.2 or later
  3. 3. Review the official Rancher upgrade documentation and release notes for your target version before proceeding
  4. 4. Perform a backup of your Rancher environment following standard backup procedures
  5. 5. Execute the upgrade using your chosen method (Helm upgrade, Docker upgrade, or Rancher UI if available)
  6. 6. Verify the upgrade was successful by checking the Rancher version and confirming all system components are healthy
  7. 7. If you have audit logging enabled with AUDIT_LEVEL >= 1, review the audit logs to confirm sensitive data is no longer being logged
Caveat Always review release notes before upgrading Rancher as there may be changes requiring configuration adjustments or deprecation notices

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

Fix this in Rancher Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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