Rancher 'Audit Log' leaks sensitive information
SUSE rancher
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/rancher/rancher Go |
|
|
SUSE rancher
| Product | Affected | Fixed in |
|---|---|---|
| github.com/rancher/rancher Go |
|
|
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.
From the CVE record · suse
SUSE Rancher may leak sensitive data into its audit logs when opt-in audit logging is enabled and AUDIT_LEVEL is set to 1 or above. The input does not specify how an attacker could access those logs or whether authentication or user interaction is required.
Teams running SUSE Rancher with github.com/rancher/rancher versions >=2.6.0 <2.6.14, >=2.7.0 <2.7.10, or >=2.8.0 <2.8.2 should check whether audit logging is enabled.