← Back
GHSA-pc2w-4mq8-32qw
Vulnerability in @dynatrace-oss/dynatrace-mcp-server (GHSA-pc2w-4mq8-32qw)
Summary
vulnerability in @dynatrace-oss/dynatrace-mcp-server (GHSA-pc2w-4mq8-32qw). Risk of unauthorized operations or information disclosure. Exploitable via ``create_dynatrace_notebook``. Mitigation: upgrade to `1.8.7` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **GHSA-pc2w-4mq8-32qw** has been found in @dynatrace-oss/dynatrace-mcp-server.
Attackers can target a specific entry point like ``create_dynatrace_notebook`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade @dynatrace-oss/dynatrace-mcp-server to **1.8.7** or later.
If unsure, ask your IT team or search "@dynatrace-oss/dynatrace-mcp-server GHSA-pc2w-4mq8-32qw" on the vendor's site.
GHSA-pc2w-4mq8-32qw (@dynatrace-oss/dynatrace-mcp-server) — CWE-862 /
Attack surface: `create_dynatrace_notebook` / `send_slack_message` / `send_email` / `send_event`
Patched: `1.8.7` — 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-862) exists in @dynatrace-oss/dynatrace-mcp-server. Attackers reach the vulnerable code path via ``create_dynatrace_notebook`` without authentication.
📍 Affected scope
@dynatrace-oss/dynatrace-mcp-server — . Attack surface: `create_dynatrace_notebook` / `send_slack_message` / `send_email` / `send_event`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **1.8.7**.
🛡️ 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 request patterns matching this CVE's known IOCs. Run `grep -r '@dynatrace-oss/dynatrace-mcp-server' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@dynatrace-oss/dynatrace-mcp-server' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `@dynatrace-oss/dynatrace-mcp-server` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade @dynatrace-oss/dynatrace-mcp-server to 1.8.7ステージング環境で 1.8.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
@dynatrace-oss/dynatrace-mcp-server
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.8.7"}]}]
References
- web https://github.com/dynatrace-oss/dynatrace-mcp/security/advisories/GHSA-pc2w-4mq8-32qw
- web https://github.com/dynatrace-oss/dynatrace-mcp/pull/529
- web https://github.com/dynatrace-oss/dynatrace-mcp/commit/2851d3ce29d834c93b67f0db903c10e0b488e7ac
- web https://github.com/dynatrace-oss/dynatrace-mcp/releases/tag/v1.8.7
- web https://github.com/advisories/GHSA-pc2w-4mq8-32qw