Horizon Alert
Summary of the vulnerability and why it matters
This issue impacts Grafana Enterprise and Cloud users with a specific configuration enabling SCIM provisioning. If exploited, it could allow unauthorized users to impersonate others or escalate their privileges within Grafana, potentially affecting access to sensitive data. The primary concern is confirming if this specific configuration is in use.
- User impersonation or privilege escalation possible.
- Affects automated user management if SCIM is enabled.
- Confirm if SCIM provisioning is configured.
Attack Path
How an attacker could exploit the issue
An attacker could leverage a compromised or malicious SCIM client to provision users with an external ID that matches an internal user ID. This would allow them to impersonate existing users and potentially gain elevated privileges within Grafana.
- SCIM provisioning must be enabled.
- A SCIM client can assign a numeric external ID.
- User impersonation or privilege escalation.
Live Threat
Current exploitation, exposure, and threat context
When Grafana's SCIM provisioning is enabled and configured, a compromised SCIM client could provision a user with a numeric `externalId`. This could allow an attacker to impersonate internal users or escalate privileges by overriding internal user IDs. This vulnerability specifically affects Grafana Enterprise and Grafana Cloud versions where the `enableSCIM` feature flag is true and `user_sync_enabled` is set to true in the `[auth.scim]` configuration block.
- User accounts and internal IDs at risk.
- Compromised SCIM client could override IDs.
- Potential user impersonation and privilege escalation.
Operational Fix
Recommended remediation, mitigation, and detection steps
In real-world deployments, Grafana Enterprise and Grafana Cloud application owners or platform teams are likely responsible for managing SCIM provisioning. The first practical step is to identify all instances of Grafana where SCIM provisioning is enabled and configured, confirm their exposure, and then coordinate with the accountable owner to plan remediation based on the business criticality.
- Application or platform owners should own.
- Verify SCIM provisioning configuration first.
- Plan remediation based on identified risk.