Skip to content

Grafana Escalation from admin to server admin when auth proxy is used

Moderate severity GitHub Reviewed Published Sep 20, 2022 in grafana/grafana • Updated Aug 7, 2024

Package

gomod github.com/grafana/grafana (Go)

Affected versions

>= 9.1.0, < 9.1.6
>= 9.0.0, < 9.0.9
< 8.5.13

Patched versions

9.1.6
9.0.9
8.5.13

Description

Today we are releasing Grafana 9.1.6, 9.0.9, 8.5.13. This patch release includes a Moderate severity security fix for CVE-2022-35957 that affects Grafana instances which are using Grafana Auth Proxy.

Release 9.1.6, latest patch, also containing security fix:

Release 9.0.9, only containing security fix:

Release 8.5.13, only containing security fix:

Appropriate patches have been applied to Grafana Cloud and as always, we closely coordinated with all cloud providers licensed to offer Grafana Pro. They have received early notification under embargo and confirmed that their offerings are secure at the time of this announcement. This is applicable to Amazon Managed Grafana and Azure's Grafana as a service offering.

Privilege escalation (CVE-2022-35957)

Summary

On August 9 an internal security review identified a vulnerability in the Grafana which allows an escalation from Admin privileges to Server Admin when Auth proxy authentication is used.

Auth proxy allows to authenticate a user by only providing the username (or email) in a X-WEBAUTH-USER HTTP header: the trust assumption is that a front proxy will take care of authentication and that Grafana server is publicly reachable only with this front proxy.

Datasource proxy breaks this assumption:

  • it is possible to configure a fake datasource pointing to a localhost Grafana install with a X-WEBAUTH-USER HTTP header containing admin username.
  • This fake datasource can be called publicly via this proxying feature.

The CVSS score for this vulnerability is 6.6 Moderate (CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H).

Impacted versions

All Grafana installations where the Auth Proxy is used.

Solutions and mitigations

To fully address CVE-2022-35957 please upgrade your Grafana instances. They are only required if you are using Auth proxy. If you can’t upgrade, as an alternative, you can deactivate the auth proxy.

Appropriate patches have been applied to Grafana Cloud.

Timeline

Here is a timeline starting from when we originally learned of the issue.

  • 2022-08-09: Vulnerability is reported as a result of an Internal security audit.
  • 2022-08-09: Release timeline determined: 2022-09-06 for private customer release, 2022-09-20 for public release.
  • 2022-08-09: Confirmed that Grafana Cloud is not impacted.
  • 2022-09-06: Private release.
  • 2022-09-20: Public release.

Reporting security issues

If you think you have found a security vulnerability, please send a report to [email protected]. This address can be used for all of Grafana Labs' open source and commercial products (including, but not limited to Grafana, Grafana Cloud, Grafana Enterprise, and grafana.com). We can accept only vulnerability reports at this address. We would prefer that you encrypt your message to us by using our PGP key. The key fingerprint is

F988 7BEA 027A 049F AE8E 5CAA D125 8932 BE24 C5CA

The key is available from keyserver.ubuntu.com.

Security announcements

We maintain a security category on our blog, where we will always post a summary, remediation, and mitigation details for any patch containing security fixes.

You can also subscribe to our RSS feed.

References

@vtorosyan vtorosyan published to grafana/grafana Sep 20, 2022
Published by the National Vulnerability Database Sep 20, 2022
Published to the GitHub Advisory Database May 14, 2024
Reviewed May 14, 2024
Last updated Aug 7, 2024

Severity

Moderate

EPSS score

0.276%
(69th percentile)

Weaknesses

CVE ID

CVE-2022-35957

GHSA ID

GHSA-ff5c-938w-8c9q

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.