Cloudflare Dex Analysis
Digital Experience Monitoring (DEX) provides visibility into device, network, and application performance across your Zero Trust organization.
0Tools
3Findings
3.6kStars
—Downloads
Mar 22, 2026Last Scanned
Findings3
1critical
1high
0medium
1low
0informational
criticalQ13MCP Bridge Package Supply Chain AttackMCP10-supply-chainAML.T0054
Pattern "(?:mcp|fastmcp|langchain-mcp|llama-index-mcp)(?:>=|~=|==)?(?!\d)" matched in source_code: "mcp" (at position 55)
MCP bridge packages (mcp-remote, mcp-proxy, @modelcontextprotocol/sdk, fastmcp) are high-value supply chain targets — CVE-2025-6514 (CVSS 9.6) in mcp-remote affected 437,000+ installs. Always pin exact versions (no ^ or ~ ranges). Use lockfiles (package-lock.json, pnpm-lock.yaml, uv.lock). Never run `npx mcp-remote` without version pinning. Verify package integrity with `npm audit` or `pip-audit` before deployment. Reference: CVE-2025-6514, OWASP ASI04.
highL8Version Rollback / Downgrade AttackMCP10-supply-chainAML.T0017
Pattern "["'](?:overrides|resolutions|pnpm\.overrides)["']\s*:\s*\{[^}]*["'][\w@/-]+["']\s*:\s*["'](?:0\.|1\.0|<=|<\d)" matched in source_code: ""overrides": {
"esbuild": "0." (at position 1481)
Use 'npm ci' (not 'npm install') in CI to enforce lockfile integrity. Enable npm audit signatures to verify package provenance. Pin all direct dependencies to exact versions. Use SLSA provenance verification for critical dependencies. Monitor lockfile changes in pull requests with automated diff review. Never use --force or --legacy-peer-deps in production CI.
lowF4MCP Spec Non-ComplianceMCP07-insecure-config
Server fails MCP spec compliance checks: required:server_name; required:server_version; required:protocol_version; recommended:tool_descriptions; recommended:parameter_descriptions
Follow the MCP specification for server metadata. Include server name, version, and protocol version. Provide descriptions for all tools and parameters.
Tools
No tools exposed by this server.
Security Category Deep Dive
Sub-Category Tree · Remediation Roadmap · Attack Stories · Compliance Overlay · ATLAS Techniques · Maturity Model
Prompt Injection
Prompt & context manipulation attacks
69
Maturity
14
Rules
5
Sub-Categories
1
Gaps
64%
Implemented
56
Tests
1
Stories
100%3 rules
Injection via tool descriptions and parameter fields
GAP-001Prompt Injection Coverage GapMissing detection coverage for emerging prompt injection attack variants not addressed by current rules
100%4 rules
Hidden instructions via external content and tool responses
100%2 rules
Context window saturation and prior-approval exploitation
100%3 rules
Payload hiding via invisible chars, base64, schema fields
100%2 rules
Injection via prompt templates and runtime tool output