GPU VulnDB

Database/Control plane, storage & DevOps

Grafana: datasource query caching stores grafana_session headers, leaking user sessions

CVSS 8.8CVE-2022-23498Control plane, storage & DevOpscurated

Impact

With datasource query caching enabled, Grafana caches all request headers including grafana_session. Any user who queries a cached datasource can retrieve another user's session token and act as that user. On a GPU fleet Grafana is usually the shared observability front end for DCGM, fabric and scheduler metrics, and often the same instance serves operators and tenants; a stolen session can escalate from a tenant view to an admin view, and Grafana admin typically means access to datasource credentials for the metrics and logging backends behind it. Impact is confined to the monitoring plane - it does not touch GPU nodes directly - but it is a credible path to operator-level visibility and stored datasource secrets.

Who can reach it

Any authenticated Grafana user who can run a query against a datasource that has query caching enabled.

What to do

Upgrade Grafana to 9.2.10 or 9.3.4 and restart the service - a single daemon restart on the monitoring host, no impact on GPU workloads. If an upgrade cannot be scheduled immediately, disable datasource query caching on all datasources, and rotate Grafana sessions and any datasource credentials that may have been reachable.

References

Related entries

All Control plane, storage & DevOps entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.