← Back
GHSA-xrmj-5g4g-8987
Vulnerability in @dynatrace-oss/dynatrace-mcp-server (GHSA-xrmj-5g4g-8987)
Summary
vulnerability in @dynatrace-oss/dynatrace-mcp-server (GHSA-xrmj-5g4g-8987). Risk of unauthorized operations or information disclosure. Exploitable via `GET /platform/automation/v1/workflows/`. Mitigation: upgrade to `2.0.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **GHSA-xrmj-5g4g-8987** has been found in @dynatrace-oss/dynatrace-mcp-server.
Attackers can target a specific entry point like `GET /platform/automation/v1/workflows/` 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 **2.0.0** or later.
If unsure, ask your IT team or search "@dynatrace-oss/dynatrace-mcp-server GHSA-xrmj-5g4g-8987" on the vendor's site.
GHSA-xrmj-5g4g-8987 (@dynatrace-oss/dynatrace-mcp-server) — CWE-1336 /
Attack surface: GET /platform/automation/v1/workflows/ / `create_workflow_for_notification` / `teamName` / `problemType`
Patched: `2.0.0` — 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-1336) exists in @dynatrace-oss/dynatrace-mcp-server. Attackers reach the vulnerable code path via `GET /platform/automation/v1/workflows/` without authentication.
📍 Affected scope
@dynatrace-oss/dynatrace-mcp-server — . Attack surface: GET /platform/automation/v1/workflows/ / `create_workflow_for_notification` / `teamName` / `problemType`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **2.0.0**.
🛡️ 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 `GET /platform/automation/v1/workflows/` requests with malformed payloads or SQL meta-characters. 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 し、稼働しているサービス・バージョンを把握する。
-
3Hunt for indicators of compromise detect
grep 'GET /platform/automation/v1/workflows/' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `GET /platform/automation/v1/workflows/` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
6Apply patch patch
Upgrade @dynatrace-oss/dynatrace-mcp-server to 2.0.0ステージング環境で 2.0.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Replay attack against GET /platform/automation/v1/workflows/ on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
@dynatrace-oss/dynatrace-mcp-server
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.0.0"}]}]
References
- web https://github.com/dynatrace-oss/dynatrace-mcp/security/advisories/GHSA-xrmj-5g4g-8987
- web https://github.com/dynatrace-oss/dynatrace-mcp/pull/547
- web https://github.com/dynatrace-oss/dynatrace-mcp/commit/64dfcb1095823d0fb43013635446288a6ff60e29
- web https://github.com/dynatrace-oss/dynatrace-mcp/releases/tag/v2.0.0
- web https://github.com/advisories/GHSA-xrmj-5g4g-8987