CyberRota Analysis
AI-GeneratedThe local OAuth helper in dbt-mcp prior to version 1.20.0 is vulnerable due to an unauthenticated endpoint that exposes sensitive tokens, including access and refresh tokens, without proper Host validation. This flaw allows remote attackers to exploit DNS rebinding to access the tokens, granting them unauthorized access to the dbt Platform API, which could lead to the compromise of projects and sensitive account data. Organizations using dbt-mcp should prioritize upgrading to version 1.20.0 to mitigate this risk.
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
dbt-mcp is a Model Context Protocol server for interacting with dbt. Prior to 1.20.0, the local OAuth helper in src/dbt_mcp/oauth/fastapi_app.py exposes GET /dbt_platform_context without authentication or Host validation after a user completes the dbt Platform OAuth flow. The endpoint returns the full DbtPlatformContext, including access_token and refresh_token values persisted by the context manager, to any process that can reach 127.0.0.1:6785. The absence of TrustedHostMiddleware allows a remote attacker to use DNS rebinding against a victim's browser because the helper accepts arbitrary Host headers, while a co-located process can request the endpoint directly. The stolen tokens provide immediate dbt Platform API access as the victim and persistent access through the refresh token, allowing access to or modification of projects, jobs, environment secrets, and related account data. This issue is fixed in version 1.20.0.