CyberRota Analysis
AI-GeneratedThe MCP plugin of python-utcp versions up to 1.1.2 is vulnerable due to a lack of secure URL validation for HTTP and WebSocket server connections, allowing potential interception of the MCP handshake and enabling cleartext connections to internal hosts. While the risk of exploitation is limited due to the nature of the MCP handshake and the configuration being operator-authored, organizations using this plugin should prioritize upgrading to version 1.1.3 to mitigate the risk of unauthorized access. This vulnerability is particularly relevant for developers and system administrators managing MCP server configurations.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
utcp-mcp (the MCP plugin of python-utcp) through 1.1.2 connects to the HTTP and WebSocket MCP server URLs given in a call template's mcpServers configuration without the ensure_secure_url validation that the HTTP-family plugins apply, so the HTTPS/WSS-or-loopback rule is not enforced. A call template naming a plain-HTTP, non-loopback MCP server URL is dialed as configured, exposing the MCP handshake to network interception and permitting cleartext connections to internal hosts. The mcpServers configuration is operator-authored rather than remote data, and the connection is an MCP handshake rather than an arbitrary request returning a body, which limits practical exploitation; the OAuth2 token_url credential path described in the original report was not reachable in the affected versions, because the OAuth2 handler was never invoked and the call template's auth field was not read. Fixed in utcp-mcp 1.1.3, which validates server URLs before any connection is made.