Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2023-6152

Authorization Flaw in github.com/grafana/grafana (CVE-2023-6152)

Summary

Vulnerability in github.com/grafana/grafana (CVE-2023-6152). Risk of unauthorized operations or information disclosure. Exploitable via PUT /api/user. Mitigation: upgrade to 10.3.3 or later.

Original description

The description as published by the source.

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.

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
  • Warni…

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2023-6152 has been found in github.com/grafana/grafana.
Attackers can target a specific entry point like PUT /api/user over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/grafana/grafana to 10.3.3 or later.
If unsure, ask your IT team or search "github.com/grafana/grafana CVE-2023-6152" on the vendor's site.

CVE-2023-6152 (github.com/grafana/grafana) — CWE-863
Attack vector: remote (network-reachable) / no user interaction
Attack surface: PUT /api/user / verify_email_enabled / false
Patched: 10.3.3 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Incorrect authorization (CWE-863) exists in github.com/grafana/grafana. Attackers reach the vulnerable code path via PUT /api/user.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/grafana/grafana. Attack surface: PUT /api/user / verify_email_enabled / false.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 10.3.3.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual PUT /api/user requests with malformed payloads or SQL meta-characters. Run grep -r 'github.com/grafana/grafana' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'github.com/grafana/grafana' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/grafana/grafana を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Hunt for indicators of compromise detect 
    grep 'PUT /api/user' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで PUT /api/user への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply patch patch 
    Upgrade github.com/grafana/grafana to 10.3.3

    ステージング環境で 10.3.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  4. 4
    Post-deployment verification verify 
    Replay attack against PUT /api/user on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

Go github.com/grafana/grafana
[{"type":"SEMVER","events":[{"introduced":"10.3.0"},{"fixed":"10.3.3"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details