VulnerableCode Package Details - pkg:rpm/redhat/grafana@9.0.9-2?arch=el9

Vulnerabilities affecting this package (5)

Vulnerability	Summary	Fixed by
VCID-1rsj-pm1p-qbd6 Aliases: CVE-2022-2880	Multiple vulnerabilities have been discovered in Go, the worst of which could lead to remote code execution.	There are no reported fixed by versions.
VCID-azr4-u36f-pbew Aliases: CVE-2022-27664 GHSA-69cg-p879-7622	Multiple vulnerabilities have been discovered in Go, the worst of which could result in denial of service.	There are no reported fixed by versions.
VCID-fb5p-kja2-6fbb Aliases: CVE-2022-39229 GHSA-gj7m-853r-289r	Grafana when using email as a username can block other users from signing in Today we are releasing Grafana 9.2. Alongside with new features and other bug fixes, this release includes a Moderate severity security fix for CVE-2022-39229 We are also releasing security patches for Grafana 9.1.8 and Grafana 8.5.14 to fix these issues. Release 9.2, latest release, also containing security fix: - [Download Grafana 9.2](https://grafana.com/grafana/download/9.2) Release 9.1.8, only containing security fix: - [Download Grafana 9.1.8](https://grafana.com/grafana/download/9.1.8) Release 8.5.14, only containing security fix: - [Download Grafana 8.5.14](https://grafana.com/grafana/download/8.5.14) Appropriate patches have been applied to [Grafana Cloud](https://grafana.com/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. ## Improper authentication - CVE-2022-39229 ### Summary On September 7 as a result of an internal security audit we have discovered a security vulnerability in Grafana basic authentication, related to the usage of username and email address. In Grafana, a user’s username and email address are unique fields, that means no other user can have the same username or email address as another user. In addition, a user can have an email address as a username and Grafana login allows users to sign in with either username or email address. This creates an unusual behavior, where _user_1_ can register with one email address and _user_2_ can register their username as _user_1_’s email address. As a result, _user_1_ would be prevented to sign in Grafana, since _user_1_ password won’t match with _users_2_ email address. The CVSS score for this vulnerability is 4.3 Moderate (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L). ### Impacted versions All installations for Grafana versions <=9.x, <=8.x ### Solutions and mitigations To fully address CVE-2022-39229 please upgrade your Grafana instances. Appropriate patches have been applied to [Grafana Cloud](https://grafana.com/cloud). ## Reporting security issues If you think you have found a security vulnerability, please send a report to security@grafana.com. 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](https://community.grafana.com/c/support/security-announcements) 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](https://grafana.com/tags/security/index.xml).	There are no reported fixed by versions.
VCID-rtb8-bayb-dfbn Aliases: CVE-2022-41715	Multiple vulnerabilities have been discovered in Go, the worst of which could lead to remote code execution.	There are no reported fixed by versions.
VCID-wkvy-hjee-nyh8 Aliases: CVE-2022-35957 GHSA-ff5c-938w-8c9q	Grafana Escalation from admin to server admin when auth proxy is used 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](https://grafana.com/docs/grafana/latest/setup-grafana/configure-security/configure-authentication/auth-proxy/#configure-auth-proxy-authentication). Release 9.1.6, latest patch, also containing security fix: - [Download Grafana 9.1.6](https://grafana.com/grafana/download/9.1.6) - [Release notes](https://grafana.com/docs/grafana/latest/release-notes/release-notes-9-1-6/) Release 9.0.9, only containing security fix: - [Download Grafana 9.0.9](https://grafana.com/grafana/download/9.0.9) - [Release notes](https://grafana.com/docs/grafana/latest/release-notes/release-notes-9-0-9/) Release 8.5.13, only containing security fix: - [Download Grafana 8.5.13](https://grafana.com/grafana/download/8.5.13) - [Release notes](https://grafana.com/docs/grafana/latest/release-notes/release-notes-8-5-13/) Appropriate patches have been applied to [Grafana Cloud](https://grafana.com/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](https://grafana.com/docs/grafana/latest/setup-grafana/configure-security/configure-authentication/auth-proxy/#configure-auth-proxy-authentication) 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](https://grafana.com/docs/grafana/latest/developers/http_api/data_source/#data-source-proxy-calls) 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](https://grafana.com/docs/grafana/latest/setup-grafana/configure-security/configure-authentication/auth-proxy/#configure-auth-proxy-authentication) 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](https://grafana.com/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 security@grafana.com. 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](https://community.grafana.com/c/support/security-announcements) 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](https://grafana.com/tags/security/index.xml).	There are no reported fixed by versions.

Next non-vulnerable version	None.
Latest non-vulnerable version	None.
Risk	4.0

Date	Actor	Action	Vulnerability	Source	VulnerableCode Version
2026-04-01T13:57:14.355479+00:00	RedHat Importer	Affected by	VCID-azr4-u36f-pbew	https://access.redhat.com/hydra/rest/securitydata/cve/CVE-2022-27664.json	38.0.0
2026-04-01T13:57:04.131035+00:00	RedHat Importer	Affected by	VCID-wkvy-hjee-nyh8	https://access.redhat.com/hydra/rest/securitydata/cve/CVE-2022-35957.json	38.0.0
2026-04-01T13:56:53.101767+00:00	RedHat Importer	Affected by	VCID-rtb8-bayb-dfbn	https://access.redhat.com/hydra/rest/securitydata/cve/CVE-2022-41715.json	38.0.0
2026-04-01T13:56:51.628771+00:00	RedHat Importer	Affected by	VCID-1rsj-pm1p-qbd6	https://access.redhat.com/hydra/rest/securitydata/cve/CVE-2022-2880.json	38.0.0
2026-04-01T13:56:42.472087+00:00	RedHat Importer	Affected by	VCID-fb5p-kja2-6fbb	https://access.redhat.com/hydra/rest/securitydata/cve/CVE-2022-39229.json	38.0.0