Technical impact
The flaw stems from the POST /api/v1/projects/{projectUuid}/dbt-cloud/webhook endpoint lacking authentication and sanitization. The handler accepts accountId and runId directly from a dbt Cloud job completion payload and injects them into the URL used to call the fixed‑host cloud.getdbt.com API. Because these identifiers are unsanitized, an attacker can craft an accountId that contains path traversal characters, causing the server to request attacker‑controlled paths on the same host while still transmitting the victim project’s API key in the Authorization header. The advisory notes that the provided evidence does not prove the attacker can capture the Authorization header, yet the presence of a credential‑bearing request to an attacker‑controlled path represents a serious exposure risk. Additionally, the absence of authentication allows anyone who knows a projectUuid to trigger preview creation, providing further potential for abuse.
Affected Systems
The vulnerability affects the open‑source Lightdash platform, specifically all releases through 0.3213.0. Users running these versions without a configured webhook secret are susceptible. No other vendor products are listed.
Risk and Exploitability
The CVSS score of 8.3 reflects the high impact of credential leakage and with‑in‑scope function exploitation. EPSS is not available, so the statistical likelihood of exploitation is unknown, but the absence of authentication and lack of signature validation make the attack trivial for anyone who can reach the endpoint. The vulnerability is not currently listed in the CISA Known Exploited Vulnerabilities catalog; however, its discovery and available advisory suggest it may be actively sought by threat actors. The likely attack vector is an unauthenticated HTTP POST to the webhook, requiring knowledge of a valid projectUuid and a live dbt Cloud IDE project; the UUID is not trivial to enumerate but can be discovered in shared or multi‑tenant contexts.