Service token exposure and potential privilege escalation in SUSE Observability
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| SUSE | SUSE Observability | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Suse | Suse Observability |
|
Vendor Workaround
Revoke the existing service token inside SUSE Observability. Generate a new service token assigned to the `stackstate-guest` role (which enforces read-only access) rather than the default `stackstate-k8s-troubleshooter` role.
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.219% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Suse
Suse suse Observability |
|
| Vendors & Products |
Suse
Suse suse Observability |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | The rancher-extension-stackstate extension in SUSE Observability exposes service tokens in plain configuration or insecure locations rather than managing them securely. An attacker with minimal access could obtain the token to gain unauthorized access or escalate privileges within the observability environment. | |
| Title | Service token exposure and potential privilege escalation in SUSE Observability | |
| Weaknesses | CWE-200 CWE-312 |
|
| References |
| |
| Metrics |
cvssV3_1
|