Grafana users with email as a username can block other users from signing in
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| grafana | grafana | affected |
|
Configuration 1 [-]
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat Ceph Storage 6.1 | |||
| rhceph/rhceph-6-dashboard-rhel9:6-75 | cpe:/a:redhat:ceph_storage:6.1::el9 | RHSA-2023:3642 | 2023-06-15T00:00:00Z |
| Red Hat Enterprise Linux 8 | |||
| grafana-0:7.5.15-4.el8 | cpe:/a:redhat:enterprise_linux:8 | RHSA-2023:2784 | 2023-05-16T00:00:00Z |
| Red Hat Enterprise Linux 9 | |||
| grafana-0:9.0.9-2.el9 | cpe:/a:redhat:enterprise_linux:9 | RHSA-2023:2167 | 2023-05-09T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2024-1627 | Grafana is an open source data visualization platform for metrics, logs, and traces. Versions prior to 9.1.8 and 8.5.14 allow one user to block another user's login attempt by registering someone else'e email address as a username. A Grafana 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. A user can have an email address as a username. However, the login system allows users to log in with either username or email address. Since Grafana allows a user to log in with either their username or email address, this creates an usual behavior where `user_1` can register with one email address and `user_2` can register their username as `user_1`’s email address. This prevents `user_1` logging into the application since `user_1`'s password won’t match with `user_2`'s email address. Versions 9.1.8 and 8.5.14 contain a patch. There are no workarounds for this issue. |
Github GHSA |
GHSA-gj7m-853r-289r | Grafana when using email as a username can block other users from signing in |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: 1.1% (1.143% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|