Grafana is an open-source platform for monitoring and observability. In affected versions when a data source has the Forward OAuth Identity feature enabled, sending a query to that datasource with an API token (and no other user credentials) will forward the OAuth Identity of the most recently logged-in user. This can allow API token holders to retrieve data for which they may not have intended access. This attack relies on the Grafana instance having data sources that support the Forward OAuth Identity feature, the Grafana instance having a data source with the Forward OAuth Identity feature toggled on, the Grafana instance having OAuth enabled, and the Grafana instance having usable API keys. This issue has been patched in versions 7.5.13 and 8.3.4.
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Grafana | Grafana | 7.2.0 (including) | 7.5.13 (excluding) |
| Grafana | Grafana | 8.0.0 (including) | 8.3.4 (excluding) |
| Red Hat Ceph Storage 5.2 | RedHat | rhceph/rhceph-5-dashboard-rhel8:5-56 | * |
| Red Hat Enterprise Linux 8 | RedHat | grafana-0:7.5.15-3.el8 | * |
| Red Hat Enterprise Linux 9 | RedHat | grafana-0:7.5.15-3.el9 | * |
| Red Hat OpenShift Container Platform 4.10 | RedHat | openshift4/ose-grafana:v4.10.0-202202160023.p0.g48aec35.assembly.stream | * |
| Grafana | Ubuntu | esm-apps/xenial | * |
| Grafana | Ubuntu | trusty | * |
| Grafana | Ubuntu | xenial | * |
There are many different kinds of mistakes that introduce information exposures. The severity of the error can range widely, depending on the context in which the product operates, the type of sensitive information that is revealed, and the benefits it may provide to an attacker. Some kinds of sensitive information include:
Information might be sensitive to different parties, each of which may have their own expectations for whether the information should be protected. These parties include:
Information exposures can occur in different ways:
It is common practice to describe any loss of confidentiality as an “information exposure,” but this can lead to overuse of CWE-200 in CWE mapping. From the CWE perspective, loss of confidentiality is a technical impact that can arise from dozens of different weaknesses, such as insecure file permissions or out-of-bounds read. CWE-200 and its lower-level descendants are intended to cover the mistakes that occur in behaviors that explicitly manage, store, transfer, or cleanse sensitive information.