T08 · Insecure Dependencies
- Location
SKILL.md:14- Finding
Unverified Third-Party Weather Gateway
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 14–16; related MCP configuration at lines 34–37
Vulnerability Type: Insecure remote service dependency
Risk Level: MediumVulnerable Code
bash curl -X POST https://gateway.pipeworx.io/weather/mcp \ -H "Content-Type: application/json" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_weather","arguments":{"latitude":37.7749,"longitude":-122.4194}}}'The same intermediary is configured as the MCP server:
json { "mcpServers": { "weather": { "url": "https://gateway.pipeworx.io/weather/mcp" } } }Technical Analysis
The Skill instructs users and agents to submit weather requests to
gateway.pipeworx.io, while separately stating that the service is powered by Open-Meteo. Requests are therefore routed through a third-party intermediary rather than directly to an official Open-Meteo endpoint.The project contains no source code for the gateway, integrity verification mechanism, response authentication, privacy policy, ownership verification, or documented trust justification. Consequently, the effective behavior of the remote dependency can change without any modification to the reviewed Skill. Although HTTPS protects traffic in transit against ordinary network interception, it does not protect against a malicious, compromised, or incorrectly operated gateway.
This is a supply-chain and trust-boundary risk. Weather responses returned by the gateway must be treated as untrusted remote input.
Attack Path
- A user installs or adopts the MCP configuration from
SKILL.md. - The agent sends latitude, longitude, requested forecast duration, and JSON-RPC metadata to
gateway.pipeworx.io. - The gateway operator—or an attacker who compromises the gateway—records the submitted location queries.
- The gateway can return altered, fabricated, stale, or otherwise attacker-co ...[truncated 1159 chars]
- A user installs or adopts the MCP configuration from
- Remediation
View remediation
Remediation Suggestions
- Replace the intermediary with the documented official Open-Meteo HTTPS API where practical.
- If the intermediary is required, document its ownership, operational purpose, privacy and retention practices, security controls, and relationship with Open-Meteo.
- Minimize submitted location precision when exact coordinates are unnecessary and clearly disclose that coordinates are sent to a third party.
- Validate response structure, types, ranges, and forecast-day limits before using returned data.
- Treat all response fields as untrusted input and prevent them from being interpreted as agent instructions, commands, or executable content.
- Apply request timeouts, response-size limits, retry limits, and graceful failure handling.
- For security-sensitive workflows, authenticate responses or cross-check consequential weather results against an independent trusted source.
- Pin or otherwise govern the remote service contract so unexpected changes are detected and reviewed.
