GHSA-pc2w-4mq8-32qw: @dynatrace oss/dynatrace mcp server @dynatrace-oss/dynatrace-mcp-server's Create_dynatrace_notebook Missing The Human-approval Vulnerability

LOW
CVSS 3.7
CWE-862
Published
Advisory Summary

GHSA-pc2w-4mq8-32qw is a LOW (CVSS 3.7) @dynatrace-oss/dynatrace-mcp-server's create_dynatrace_notebook missing the human-approval vulnerability (CWE-862: Missing Authorization) affecting @dynatrace oss/dynatrace mcp server libraries in the npm ecosystem. The issue involves @dynatrace-oss/dynatrace-mcp-server's create_dynatrace_notebook missing the human-approval gate. Remediation is available by upgrading affected packages to version 1.8.7.

GHSA-pc2w-4mq8-32qw at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-pc2w-4mq8-32qw
Severity LOW
CVSS v3.1 Base Score 3.7
CWE Classification CWE-862: Missing Authorization
Affected Product @dynatrace oss/dynatrace mcp server
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 3.7

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity Low (I:L)
Availability None (A:N)

How to Fix GHSA-pc2w-4mq8-32qw

To remediate this vulnerability, upgrade all affected @dynatrace oss/dynatrace mcp server dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

@dynatrace-oss/dynatrace-mcp-server fixed: 1.8.7
npm install @dynatrace-oss/dynatrace-mcp-server@1.8.7
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls @dynatrace-oss/dynatrace-mcp-server

How to Check if You Are Affected

To determine whether your Node.js application is affected by GHSA-pc2w-4mq8-32qw, inspect your project dependencies using npm:

npm ls @dynatrace-oss/dynatrace-mcp-server

Analyze the terminal output to locate any version of @dynatrace oss/dynatrace mcp server in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.8.7), your application is affected.

Note: The npm ls @dynatrace-oss/dynatrace-mcp-server command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-862: Missing Authorization, where the product does not perform an authorization check when an actor attempts to access a resource or perform an action. In @dynatrace oss/dynatrace mcp server, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary A missing human-approval gate on the `create_dynatrace_notebook` tool allows a caller to create persistent tenant-visible documents containing arbitrary content (including embedded DQL that other users execute when opening the notebook) without operator consent. ### Details `dynatrace-mcp-server` registers six write tools: `send_slack_message`, `send_email`, `send_event`, `create_workflow_for_notification`, `make_workflow_public`, and `create_dynatrace_notebook`. Five of these call `requestHumanApproval()` before executing the side-effect, which elicits the operator's explicit consent through the MCP elicitation protocol. The CHANGELOG explicitly states these approval gates were added "to ensure user consent and prevent unintended actions." `create_dynatrace_notebook` does not call `requestHumanApproval()`. The tool was introduced in a separate release from the approval-gate retrofit and was left ungated. As a result, a caller can create persistent, tenant-visible Dynatrace notebooks containing arbitrary content with no operator confirmation. Notebooks can include embedded DQL queries that later execute under the permissions of any tenant user who opens them. The vulnerable code is in `src/index.ts`, lines 1563-1601: ```typescript tool( 'create_dynatrace_notebook', 'Create Dynatrace Notebook', 'Create a new notebook in the Dynatrace platform ...', { name: z.string().describe(/* ... */), description: z.string().optional().describe(/* ... */), content: z.array(z.object({ type: z.enum(['dql', 'markdown']), text: z.string(), })).describe(/* ... */), }, { readOnlyHint: false, }, async ({ name, content, description }) => { const dtClient = await createAuthenticatedHttpClient(allRequiredScopes); const data = await createDynatraceNotebook(dtClient, name, content, description); // No requestHumanApproval() call. // No destructiveHint annotation. // Scopes requested are allRequiredScopes (the broadest possible set) // even though only document:documents:write is needed. return data ? `Document created successfully: ${dtEnvironment}/ui/apps/dynatrace.notebooks/notebook/${data.id}` : 'document creation failed'; }, ); ``` By comparison, every other write tool calls `requestHumanApproval()` as its first action: - `send_email` (line 1274): `const approved = await requestHumanApproval(...);` - `send_slack_message` (line 652): `const approved = await requestHumanApproval(...);` - `send_event` (line 1367): `const approved = await requestHumanApproval(...);` - `create_workflow_for_notification` (line 1069): `const approved = await requestHumanApproval(...);` - `make_workflow_public` (line 1118): `const approved = await requestHumanApproval(...);` ### PoC Tested end-to-end against a real Dynatrace tenant. The MCP server was started in HTTP mode with the operator's Platform Token: ```bash export DT_ENVIRONMENT=https://<tenant>.apps.dynatrace.com export DT_PLATFORM_TOKEN=dt0s16.... npx -y @dynatrace-oss/dynatrace-mcp-server@1.8.5 --http --port 3000 ``` A single unauthenticated POST from a process with no Dynatrace credentials of its own: ```bash curl -sS http://127.0.0.1:3000/ \ -H 'Content-Type: application/json' \ -H 'Accept: application/json, text/event-stream' \ -d '{ "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "create_dynatrace_notebook", "arguments": { "name": "Unapproved notebook", "description": "Created without operator approval.", "content": [ {"type": "markdown", "text": "# This notebook was created without approval"}, {"type": "dql", "text": "fetch logs | limit 10"} ] } } }' ``` The response: ``` event: message data: {"result":{"content":[{"type":"text","text":"Document created successfully: https://<tenant>.apps.dynatrace.com/ui/apps/dynatrace.notebooks/notebook/<uuid>"}]}, "jsonrpc":"2.0","id":1} ``` The notebook is visible in the operator's Notebooks app within seconds. No elicitation prompt was sent to any operator client. By contrast, the same harness invoking `send_email` or `send_slack_message` returns: ``` "Operation cancelled: Human approval was not granted for sending this email." ``` The gate logic exists and is wired up for all other write tools - it is simply missing on `create_dynatrace_notebook`. ### Impact - A caller (an unauthenticated network attacker over the HTTP transport when authentication is missing, or a prompt-injected LLM in stdio mode) can silently create persistent tenant-visible documents. - The notebook content is attacker-controlled. Embedded DQL queries execute under the permissions of any tenant user who later opens the notebook - a stored-DQL pattern that crosses identity boundaries within the tenant.

GHSA-pc2w-4mq8-32qw Affected @dynatrace oss/dynatrace mcp server Versions

1 component(s)
Fixed Versions:
1.8.7
Product / Package Ecosystem Affected Versions Fixed Version
@dynatrace-oss/dynatrace-mcp-server
npm
< 1.8.7
1.8.7

References

Frequently Asked Questions

What is GHSA-pc2w-4mq8-32qw?
GHSA-pc2w-4mq8-32qw is a security vulnerability in @dynatrace oss/dynatrace mcp server involving @dynatrace-oss/dynatrace-mcp-server's create_dynatrace_notebook missing the human-approval gate under CWE-862: Missing Authorization.
Which @dynatrace oss/dynatrace mcp server versions are affected?
Affected versions include releases prior to 1.8.7 across affected packages: @dynatrace-oss/dynatrace-mcp-server.
What version fixes GHSA-pc2w-4mq8-32qw?
Upgrading to 1.8.7 (or the latest patched release for your respective branch) resolves the vulnerability.
Is @dynatrace-oss/dynatrace-mcp-server affected?
Yes, @dynatrace-oss/dynatrace-mcp-server is affected in releases prior to 1.8.7. Upgrade your dependency to 1.8.7 or later.
What is the CVSS score of GHSA-pc2w-4mq8-32qw?
GHSA-pc2w-4mq8-32qw has a CVSS v3.1 base score of 3.7 (LOW) with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N.
What CWE is associated with GHSA-pc2w-4mq8-32qw?
GHSA-pc2w-4mq8-32qw is classified under CWE-862: Missing Authorization (The product does not perform an authorization check when an actor attempts to access a resource or perform an action.).
How can I check npm dependencies for GHSA-pc2w-4mq8-32qw?
Run the dependency tree command: 'npm ls @dynatrace-oss/dynatrace-mcp-server'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-pc2w-4mq8-32qw",
  "modified" : "2026-07-29T15:36:19Z",
  "published" : "2026-07-29T15:36:19Z",
  "aliases" : [ ],
  "summary" : "@dynatrace-oss/dynatrace-mcp-server's create_dynatrace_notebook missing the human-approval gate",
  "details" : "### Summary\nA missing human-approval gate on the `create_dynatrace_notebook` tool allows a caller to create persistent tenant-visible documents containing arbitrary content (including embedded DQL that other users execute when opening the notebook) without operator consent.\n\n### Details\n`dynatrace-mcp-server` registers six write tools: `send_slack_message`, `send_email`, `send_event`, `create_workflow_for_notification`, `make_workflow_public`, and `create_dynatrace_notebook`. Five of these call `requestHumanApproval()` before executing the side-effect, which elicits the operator's explicit consent through the MCP elicitation protocol. The CHANGELOG explicitly states these approval gates were added \"to ensure user consent and prevent unintended actions.\"\n\n`create_dynatrace_notebook` does not call `requestHumanApproval()`. The tool was introduced in a separate release from the approval-gate retrofit and was left ungated. As a result, a caller can create persistent, tenant-visible Dynatrace notebooks containing arbitrary content with no operator confirmation. Notebooks can include embedded DQL queries that later execute under the permissions of any tenant user who opens them.\n\nThe vulnerable code is in `src/index.ts`, lines 1563-1601:\n\n```typescript\ntool(\n  'create_dynatrace_notebook',\n  'Create Dynatrace Notebook',\n  'Create a new notebook in the Dynatrace platform ...',\n  {\n    name: z.string().describe(/* ... */),\n    description: z.string().optional().describe(/* ... */),\n    content: z.array(z.object({\n      type: z.enum(['dql', 'markdown']),\n      text: z.string(),\n    })).describe(/* ... */),\n  },\n  {\n    readOnlyHint: false,\n  },\n  async ({ name, content, description }) => {\n    const dtClient = await createAuthenticatedHttpClient(allRequiredScopes);\n    const data = await createDynatraceNotebook(dtClient, name, content, description);\n    // No requestHumanApproval() call.\n    // No destructiveHint annotation.\n    // Scopes requested are allRequiredScopes (the broadest possible set)\n    // even though only document:documents:write is needed.\n\n    return data\n      ? `Document created successfully: ${dtEnvironment}/ui/apps/dynatrace.notebooks/notebook/${data.id}`\n      : 'document creation failed';\n  },\n);\n```\n\nBy comparison, every other write tool calls `requestHumanApproval()` as its first action:\n\n- `send_email` (line 1274): `const approved = await requestHumanApproval(...);`\n- `send_slack_message` (line 652): `const approved = await requestHumanApproval(...);`\n- `send_event` (line 1367): `const approved = await requestHumanApproval(...);`\n- `create_workflow_for_notification` (line 1069): `const approved = await requestHumanApproval(...);`\n- `make_workflow_public` (line 1118): `const approved = await requestHumanApproval(...);`\n\n\n### PoC\nTested end-to-end against a real Dynatrace tenant. The MCP server was started in HTTP mode with the operator's Platform Token:\n\n```bash\nexport DT_ENVIRONMENT=https://<tenant>.apps.dynatrace.com\nexport DT_PLATFORM_TOKEN=dt0s16....\nnpx -y @dynatrace-oss/dynatrace-mcp-server@1.8.5 --http --port 3000\n```\n\nA single unauthenticated POST from a process with no Dynatrace credentials of its own:\n\n```bash\ncurl -sS http://127.0.0.1:3000/ \\\n  -H 'Content-Type: application/json' \\\n  -H 'Accept: application/json, text/event-stream' \\\n  -d '{\n    \"jsonrpc\": \"2.0\", \"id\": 1, \"method\": \"tools/call\",\n    \"params\": {\n      \"name\": \"create_dynatrace_notebook\",\n      \"arguments\": {\n        \"name\": \"Unapproved notebook\",\n        \"description\": \"Created without operator approval.\",\n        \"content\": [\n          {\"type\": \"markdown\", \"text\": \"# This notebook was created without approval\"},\n          {\"type\": \"dql\",      \"text\": \"fetch logs | limit 10\"}\n        ]\n      }\n    }\n  }'\n```\n\nThe response:\n\n```\nevent: message\ndata: {\"result\":{\"content\":[{\"type\":\"text\",\"text\":\"Document created successfully:\n       https://<tenant>.apps.dynatrace.com/ui/apps/dynatrace.notebooks/notebook/<uuid>\"}]},\n       \"jsonrpc\":\"2.0\",\"id\":1}\n```\n\nThe notebook is visible in the operator's Notebooks app within seconds. No elicitation prompt was sent to any operator client.\n\nBy contrast, the same harness invoking `send_email` or `send_slack_message` returns:\n\n```\n\"Operation cancelled: Human approval was not granted for sending this email.\"\n```\n\nThe gate logic exists and is wired up for all other write tools - it is simply missing on `create_dynatrace_notebook`.\n\n\n### Impact\n- A caller (an unauthenticated network attacker over the HTTP transport when authentication is missing, or a prompt-injected LLM in stdio mode) can silently create persistent tenant-visible documents.\n- The notebook content is attacker-controlled. Embedded DQL queries execute under the permissions of any tenant user who later opens the notebook - a stored-DQL pattern that crosses identity boundaries within the tenant.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@dynatrace-oss/dynatrace-mcp-server"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.8.7"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/dynatrace-oss/dynatrace-mcp/security/advisories/GHSA-pc2w-4mq8-32qw"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/dynatrace-oss/dynatrace-mcp/pull/529"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/dynatrace-oss/dynatrace-mcp/commit/2851d3ce29d834c93b67f0db903c10e0b488e7ac"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/dynatrace-oss/dynatrace-mcp"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/dynatrace-oss/dynatrace-mcp/releases/tag/v1.8.7"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-862" ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-07-29T15:36:19Z",
    "nvd_published_at" : null
  }
}