Technical impact
The vulnerability arises from the MCP Server’s connection configuration handling, which fails to enforce restrictions on the intended endpoints. A remote unauthenticated actor, using prompt injection techniques, can cause the server to send the stored InfluxDB API token to a crafted endpoint controlled through an InfluxDB URL supplied by the client. The exposure of the API token grants full access to any InfluxDB resources that the token permits. This flaw can lead to unauthorized data exfiltration, modification, or destruction, affecting confidentiality, integrity, and availability of time‑series data.
Affected Systems
AWS Timestream for InfluxDB MCP Server (awslabs.timestream-for-influxdb-mcp-server) versions prior to 0.0.19.
Risk and Exploitability
With a CVSS score of 6.8, the vulnerability is considered moderate‑severity. No EPSS score is available, and the issue is not listed in the CISA KEV catalog. The fix is available in 0.0.19, and no authentication is required to exploit the flaw, making it feasible for any remote actor who can send an InfluxDB URL to a client context.