T08 · Insecure Dependencies
- Location
SKILL.md:18- Finding
Unverified Third-Party MCP Service Creates a Supply-Chain Trust Risk
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 18-23
Vulnerability Type: Unverified remote MCP dependency
Risk Level: Mediumjson { "mcpServers": { "cataas": { "url": "https://gateway.pipeworx.io/cataas/mcp" } } }Technical Analysis
The Skill delegates its functionality to an externally hosted MCP service at
gateway.pipeworx.io. Although the Skill is presented as a CATAAS integration, the documentation does not establish that this gateway is operated or endorsed by CATAAS. The remote MCP implementation is neither included in the project for review nor pinned to an immutable version.Consequently, the effective behavior of the Skill depends on a third-party component that can change after installation without corresponding changes to the audited file. The gateway operator—or an attacker who compromises the gateway—could observe requests, alter tool responses, or return misleading content.
The reviewed file does not contain local executable code, credentials, persistence mechanisms, or evidence that the current endpoint is malicious. This finding is therefore a supply-chain trust risk rather than confirmation of active compromise.
Attack Path
- A user installs or enables the MCP configuration from
SKILL.md. - The Agent sends
random_cat,cat_by_tag, orlist_tagsrequests tohttps://gateway.pipeworx.io/cataas/mcp. - The third-party gateway receives the requests and associated connection metadata.
- If the gateway is malicious, compromised, or subsequently modified, it can manipulate MCP responses or record information included in requests.
- The Agent or user may trust and act upon the manipulated output because it originates from the configured service.
This project does not demonstrate remote code execution or local privilege escalation through the endpoint. Such effects would require additional behavior not present in the reviewed evidence.
Impact Assessment
The remote servi ...[truncated 477 chars]
- A user installs or enables the MCP configuration from
- Remediation
View remediation
Remediation Suggestions
- Replace the gateway with a verified first-party CATAAS MCP endpoint or a locally hosted and audited MCP implementation.
- Verify and document the ownership, operational responsibility, privacy policy, and security controls of
gateway.pipeworx.io. - Pin the remote implementation to a reviewed version or immutable artifact where the MCP deployment mechanism supports it.
- Apply an outbound allowlist so the Skill can communicate only with the explicitly approved endpoint.
- Avoid transmitting credentials, personal information, internal prompts, filesystem contents, or other sensitive data in requests.
- Validate and constrain remote responses before displaying them or using them in subsequent Agent actions.
- Monitor endpoint ownership, TLS certificate changes, availability, and unexpected response-schema changes.
- Clearly disclose to users that requests and network metadata are sent to a third-party service.
