Incorrect Authorization Affecting grafana package, versions <0:7.5.11-5.el9_0
Threat Intelligence
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk ID SNYK-ALMALINUX9-GRAFANA-5639418
- published 28 May 2023
- disclosed 26 Jul 2022
Introduced: 26 Jul 2022
CVE-2022-31107 Open this link in a new tabHow to fix?
Upgrade AlmaLinux:9 grafana to version 0:7.5.11-5.el9_0 or higher.
This issue was patched in ALSA-2022:5716.
NVD Description
Note: Versions mentioned in the description apply only to the upstream grafana package and not the grafana package as distributed by AlmaLinux.
See How to fix? for AlmaLinux:9 relevant fixed versions and status.
Grafana is an open-source platform for monitoring and observability. In versions 5.3 until 9.0.3, 8.5.9, 8.4.10, and 8.3.10, it is possible for a malicious user who has authorization to log into a Grafana instance via a configured OAuth IdP which provides a login name to take over the account of another user in that Grafana instance. This can occur when the malicious user is authorized to log in to Grafana via OAuth, the malicious user's external user id is not already associated with an account in Grafana, the malicious user's email address is not already associated with an account in Grafana, and the malicious user knows the Grafana username of the target user. If these conditions are met, the malicious user can set their username in the OAuth provider to that of the target user, then go through the OAuth flow to log in to Grafana. Due to the way that external and internal user accounts are linked together during login, if the conditions above are all met then the malicious user will be able to log in to the target user's Grafana account. Versions 9.0.3, 8.5.9, 8.4.10, and 8.3.10 contain a patch for this issue. As a workaround, concerned users can disable OAuth login to their Grafana instance, or ensure that all users authorized to log in via OAuth have a corresponding user account in Grafana linked to their email address.
References
- https://errata.almalinux.org/9/ALSA-2022-5716.html
- https://errata.almalinux.org/8/ALSA-2022-5717.html
- https://access.redhat.com/security/cve/CVE-2022-31107
- https://access.redhat.com/errata/RHSA-2022:5716
- https://access.redhat.com/errata/RHSA-2022:5717
- https://github.com/grafana/grafana/security/advisories/GHSA-mx47-6497-3fv2
- https://grafana.com/docs/grafana/next/release-notes/release-notes-8-4-10/
- https://grafana.com/docs/grafana/next/release-notes/release-notes-8-5-9/
- https://grafana.com/docs/grafana/next/release-notes/release-notes-9-0-3/
- https://security.netapp.com/advisory/ntap-20220901-0010/