GHSA-pqh8-p93p-2rx7: @dynatrace oss/dynatrace mcp server @dynatrace-oss/dynatrace-mcp-server Has A DQL Injection Vulnerability
MODERATEGHSA-pqh8-p93p-2rx7 is a MODERATE (CVSS 4.3) @dynatrace-oss/dynatrace-mcp-server has a dql injection vulnerability (CWE-943: Improper Neutralization of Special Elements in Data Query Logic) affecting @dynatrace oss/dynatrace mcp server libraries in the npm ecosystem. The issue involves @dynatrace-oss/dynatrace-mcp-server has a dql injection via parameters not documented as dql. Remediation is available by upgrading affected packages to version 2.1.1.
GHSA-pqh8-p93p-2rx7 at a Glance
Security Impact
CVSS: 4.3
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N).
How to Fix GHSA-pqh8-p93p-2rx7
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.
npm install @dynatrace-oss/dynatrace-mcp-server@2.1.1
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-pqh8-p93p-2rx7, 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 2.1.1), 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-943: Improper Neutralization of Special Elements in Data Query Logic, where the product generates a query intended to access or manipulate data in a data store such as a database, but it does not neutralize or incorrectly neutralizes special elements that can modify the intended logic of the query. 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
GHSA-pqh8-p93p-2rx7 Affected @dynatrace oss/dynatrace mcp server Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
@dynatrace-oss/dynatrace-mcp-server
|
npm |
< 2.1.1
|
2.1.1
|
References
Frequently Asked Questions
What is GHSA-pqh8-p93p-2rx7?
Which @dynatrace oss/dynatrace mcp server versions are affected?
What version fixes GHSA-pqh8-p93p-2rx7?
Is @dynatrace-oss/dynatrace-mcp-server affected?
What is the CVSS score of GHSA-pqh8-p93p-2rx7?
What CWE is associated with GHSA-pqh8-p93p-2rx7?
How can I check npm dependencies for GHSA-pqh8-p93p-2rx7?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-pqh8-p93p-2rx7",
"modified" : "2026-07-31T15:56:12Z",
"published" : "2026-07-31T15:56:12Z",
"aliases" : [ ],
"summary" : "@dynatrace-oss/dynatrace-mcp-server has a DQL injection via parameters not documented as DQL",
"details" : "### Summary\nA DQL injection vulnerability in several read tools lets a caller bypass the tools' documented field-scope, time-window, and display caps by injecting DQL pipeline stages through parameters typed as identifiers.\n\n### Details\nSeveral tools interpolate caller-supplied parameters directly into DQL query strings without quoting or escaping. The affected parameters are documented in their Zod schemas as identifiers or constrained shorthand (such as `\"24h\"` timeframe values or Kubernetes UIDs) - not as DQL expressions. The interpolation lets a caller break out of string literals, append arbitrary DQL pipeline stages, and use `//` line comments (documented in the [Dynatrace DQL language reference](https://docs.dynatrace.com/docs/discover-dynatrace/platform/grail/dynatrace-query-language/dql-reference)) to discard the rest of the intended query.\n\nThe marginal-privilege ceiling is low because the operator's token also exposes `execute_dql` with full DQL access. What the injection grants is the ability to bypass the affected tools' contract: the `readOnlyHint: true` annotation that MCP clients may treat as a signal to auto-approve, the per-tool field selection (e.g., `| fields id, name, type`), the display caps (`maxProblemsToDisplay`, `maxVulnerabilitiesToDisplay`, `maxEntitiesToDisplay`), and the time-window bounds.\n\nThe vulnerable interpolations are:\n\n| File | Line | Parameter | Interpolation |\n|------|------|-----------|---------------|\n| `src/capabilities/find-monitored-entity-by-name.ts` | 23 | `entityNames[]` | `` `fetch ${entityType} \\| search \"*${entityNames.join('*\" OR \"*')}*\" \\| fieldsAdd entity.type \\| expand tags` `` |\n| `src/capabilities/find-monitored-entity-by-name.ts` | 41 | `entityNames[]` | `` `smartscapeNodes \"*\" \\| search \"*${entityNames.join('*\" OR \"*')}*\" \\| fields id, name, type` `` |\n| `src/capabilities/list-problems.ts` | 27 | `timeframe` | `` `fetch dt.davis.problems, from: now()-${timeframe}, to: now()` `` |\n| `src/capabilities/list-vulnerabilities.ts` | 19 | `timeframe` | `` `fetch security.events, from: now()-${timeframe}, to: now()` `` |\n| `src/capabilities/list-exceptions.ts` | 11 | `timeframe` | `` `fetch user.events, from: now()-${timeframe}, to: now()` `` |\n| `src/capabilities/get-events-for-cluster.ts` | 20 | `timeframe` | `` `fetch events, from: now()-${timeframe}, to: now()` `` |\n| `src/capabilities/get-events-for-cluster.ts` | 27 | `clusterId`, `kubernetesEntityId` | `` `\\| filter k8s.cluster.uid == \"${clusterId}\" or dt.entity.kubernetes_cluster == \"${kubernetesEntityId}\"` `` |\n\nAll Zod schemas for these parameters use `z.string()` or `z.array(z.string())` with no pattern validation.\n\n### PoC\n**`clusterId` - quote-and-comment break-out.** With `clusterId = 'x\" or 1==1 //'` the constructed query becomes:\n\n```\n| filter k8s.cluster.uid == \"x\" or 1==1 //\" or dt.entity.kubernetes_cluster == \"\"\n```\n\nThe first `\"` closes the string literal, `or 1==1` neutralises the filter to match every row, and `//` discards the rest of the line including the `kubernetesEntityId` guard.\n\n**`entityNames` - pipeline-stage injection.** With `entityNames = ['svc\" | fields id, name, tags //']` the constructed smartscape query becomes:\n\n```\nsmartscapeNodes \"*\" | search \"*svc\" | fields id, name, tags //*\" | fields id, name, type\n```\n\nAfter the `//` line comment, the effective query is `smartscapeNodes \"*\" | search \"*svc\" | fields id, name, tags`. The original `| fields id, name, type` stage is suppressed and replaced with the attacker's field selection - the tool returns whatever field set the attacker requests (including ones not in the tool's documented output contract).\n\n**`timeframe` - prefix injection.** With `timeframe = '30d, to: now() | fieldsAdd internal_secret //'` the list-problems query becomes:\n\n```\nfetch dt.davis.problems, from: now()-30d, to: now() | fieldsAdd internal_secret //, to: now()\n| filter isNull(dt.davis.is_duplicate) OR not(dt.davis.is_duplicate)\n...\n```\n\nA new pipeline stage is injected before the tool's intended `| filter`, and the rest of the query is commented out.\n\nThe server's own `verify_dql` tool can be used to confirm any specific injection payload parses as valid DQL.\n\n### Impact\n- A caller (typically via prompt injection of an LLM that has access to the affected tools) can bypass the tools' field-scope, time-window, and display caps.\n- The affected tools are annotated `readOnlyHint: true`, which some MCP clients treat as a signal to auto-approve. The injection turns a \"safe\" read tool into an arbitrary-DQL surface.\n- No new data access beyond what `execute_dql` already provides - the marginal impact is the auto-approval pathway and the broken tool contract, not privilege escalation.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "@dynatrace-oss/dynatrace-mcp-server"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "2.1.1"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/dynatrace-oss/dynatrace-mcp/security/advisories/GHSA-pqh8-p93p-2rx7"
}, {
"type" : "WEB",
"url" : "https://github.com/dynatrace-oss/dynatrace-mcp/pull/562"
}, {
"type" : "WEB",
"url" : "https://github.com/dynatrace-oss/dynatrace-mcp/commit/15d3546c0618ffbaeaeca477337e08e92f2151bc"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/dynatrace-oss/dynatrace-mcp"
}, {
"type" : "WEB",
"url" : "https://github.com/dynatrace-oss/dynatrace-mcp/releases/tag/v2.1.1"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-943" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-07-31T15:56:12Z",
"nvd_published_at" : null
}
}