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

Vulnerability in github.com/grafana/grafana (CVE-2023-2183)

Summary

Vulnerability in github.com/grafana/grafana (CVE-2023-2183). Risk of unauthorized operations or information disclosure. Exploitable via POST /api/alertmanager/grafana/config/api/v1/receivers/test. Mitigation: upgrade to 9.5.3 or later.

Original description

The description as published by the source.

Grafana is an open-source platform for monitoring and observability.

The option to send a test alert is not available from the user panel UI for users having the Viewer role. It is still possible for a user with the Viewer role to send a test alert using the API as the API does not check access to this function.

This might enable malicious users to abuse the functionality by sending multiple alert messages to e-mail and Slack, spamming users, prepare Phishing attack or block SMTP server.

Users may upgrade to version 9.5.3, 9.4.12, 9.3.15, 9.2.19 and 8.5.26 to receive a fix.

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-2183 has been found in github.com/grafana/grafana.
Attackers can target a specific entry point like POST /api/alertmanager/grafana/config/api/v1/receivers/test over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/grafana/grafana to 9.5.3 or later.
If unsure, ask your IT team or search "github.com/grafana/grafana CVE-2023-2183" on the vendor's site.

CVE-2023-2183 (github.com/grafana/grafana) — CWE-284
Attack vector: remote (network-reachable)
Attack surface: POST /api/alertmanager/grafana/config/api/v1/receivers/test
Patched: 9.5.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

A vulnerability (CWE-284) exists in github.com/grafana/grafana. Attackers reach the vulnerable code path via POST /api/alertmanager/grafana/config/api/v1/receivers/test.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/grafana/grafana. Attack surface: POST /api/alertmanager/grafana/config/api/v1/receivers/test.

🔥 Severity

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

🔧 How to fix

Update to 9.5.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 POST /api/alertmanager/grafana/config/api/v1/receivers/test 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 'POST /api/alertmanager/grafana/config/api/v1/receivers/test' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

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

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

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

  4. 4
    Post-deployment verification verify 
    Replay attack against POST /api/alertmanager/grafana/config/api/v1/receivers/test on staging to confirm patch closes the vector

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

Affected packages

Go github.com/grafana/grafana
[{"type":"SEMVER","events":[{"introduced":"9.5.0"},{"fixed":"9.5.3"}]}]
Bitnami grafana
[{"type":"SEMVER","events":[{"introduced":"8.0.0"},{"fixed":"8.5.26"},{"introduced":"9.0.0"},{"fixed":"9.2.19"},{"introduced":"9.3.0"},{"fixed":"9.3.15"},{"introduced":"9.4.0"},{"fixed":"9.4.12"},{"introduced":"9.5.0"},{"fixed":"9.5.3"}]}]

References

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