CyberRota Analysis
AI-GeneratedThe MySQL MCP Server prior to version 0.4.2 is vulnerable due to improper security configurations, allowing unauthenticated access to sensitive database operations and potential code execution through DNS rebinding attacks. Attackers can exploit this flaw to disclose or modify database contents, especially if the MySQL account has FILE privileges, leading to severe security breaches. Organizations using affected versions of MySQL MCP Server should prioritize upgrading to version 0.4.2 to mitigate these critical risks.
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
MySQL MCP Server is a Model Context Protocol server that enables secure interaction with MySQL databases. Prior to 0.4.2, setting MCP_TRANSPORT=sse causes src/mysql_mcp_server/server.py to construct SseServerTransport without security_settings or enable_dns_rebinding_protection, while the Starlette routes /, /sse, and /messages/ have no authentication and the service binds to 0.0.0.0 by default. A network attacker can directly reach execute_sql, or can use DNS rebinding to make a victim's browser relay same-origin requests to a locally bound service, and supply a query that reaches cursor.execute(query). This allows unauthenticated disclosure and modification of the configured database; when the MySQL account has FILE privileges, the same access can read or write server files and may enable code execution. The default stdio transport is not affected. This issue is fixed in 0.4.2.