tencentcloud-live-mcp-server
Tencent Cloud API server implemented based on Model Context Protocol (MCP)
0Tools
7Findings
Mar 24, 2026Last Scanned
3 critical · 3 high · 1 low findings detected
Security Category Deep Dive
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
Findings7
3critical
3high
1low
Critical3
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 175)
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.
criticalC13Server-Side Template InjectionMCP03-command-injection
Pattern "f['"][^'"]*\{[^}]*(?:req|input|param|args)\.[^}]*\}[^'"]*['"]" matched in source_code: "f'使用SSE传输，端口: {args.port}'" (at position 54595)
Never pass user-supplied strings directly to template engines as the template itself. Pass user data only as template variables (context). Enable autoescaping. If dynamic templates are required, use a sandboxed environment with no access to server internals.
criticalN9MCP Logging Protocol InjectionMCP01-prompt-injectionAML.T0054
Pattern "(?:logger|logging)\s*\.\s*(?:info|warning|error|debug)\s*\(\s*(?:f"|f').*(?:result|output|response|tool_output|content)" matched in source_code: "logger.info(f"获取鉴权key: result={result" (at position 2510)
Sanitize all dynamic content before including in MCP log messages. MCP logging notifications (notifications/message) are displayed in client UIs — injection payloads in log data can influence AI behavior if the client processes logs as context. Strip control characters, ANSI escape codes, newlines, and prompt injection patterns from log content. Use structured logging with separate data fields.
High3
highD1Known CVEs in DependenciesMCP08-dependency-vuln
Dependency "requests@2.32.3" has known CVEs:
Update dependencies to versions that patch known CVEs. Run 'npm audit fix' or 'pip-audit' to identify and resolve vulnerable dependencies.
highD1Known CVEs in DependenciesMCP08-dependency-vuln
Dependency "mcp@1.6.0" has known CVEs:
Update dependencies to versions that patch known CVEs. Run 'npm audit fix' or 'pip-audit' to identify and resolve vulnerable dependencies.
highM7Tool Response Structure BombASI08-agentic-dosAML.T0054
Pattern "(\+\=|concat|push|append).*\1.*\1" matched in source_code: "PushLive -直播，PullVodPushLive -点播，PullPicPushLive -图片。示例值：PullLivePush" (at position 19347)
Implement response size limits and nesting depth caps for all tool responses. Never construct responses with programmatic deep nesting or exponential expansion. CVE-2026-25048 demonstrated that nested structures can exhaust parser stacks in LLM pipelines. Set maximum response size (e.g., 100KB), maximum JSON nesting depth (e.g., 20 levels), and maximum array length. Use streaming for large responses rather than constructing them in memory.
Low1
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.