CVE-2022-35957

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:

• Download Grafana 9.1.6
• Release notes

Release 9.0.9, only containing security fix:

• Download Grafana 9.0.9
• Release notes

Release 8.5.13, only containing security fix:

• Download Grafana 8.5.13
• Release notes

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)

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.

CVE-2022-35957 has a CVSS score of 6.6 (High). The vector is network-reachable, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (9.1.6, 9.0.9, 8.5.13); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2022-35957? CVE-2022-35957 is a high-severity security vulnerability in github.com/grafana/grafana (go), affecting versions >= 9.1.0, < 9.1.6. It is fixed in 9.1.6, 9.0.9, 8.5.13.
2. How severe is CVE-2022-35957? CVE-2022-35957 has a CVSS score of 6.6 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/grafana/grafana are affected by CVE-2022-35957? github.com/grafana/grafana (go) versions >= 9.1.0, < 9.1.6 is affected.
4. Is there a fix for CVE-2022-35957? Yes. CVE-2022-35957 is fixed in 9.1.6, 9.0.9, 8.5.13. Upgrade to this version or later.
5. Is CVE-2022-35957 exploitable, and should I be worried? Whether CVE-2022-35957 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2022-35957 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2022-35957?
   • Upgrade github.com/grafana/grafana to 9.1.6 or later
   • Upgrade github.com/grafana/grafana to 9.0.9 or later
   • Upgrade github.com/grafana/grafana to 8.5.13 or later